Open source · MIT · .NET · 3 packages shipped

The first GraphQL ORM
for Sitecore headless.

Strongly-typed, Synthesis-style item models over the Sitecore GraphQL Edge — on raw HttpClient and System.Text.Json. No third-party GraphQL library.

$ dotnet add package Axlis.ORM

The package family

Three shipped families, one Sitecore ecosystem.

Reference the whole stack, or just the piece you need. Each family is independently installable.

Axlis.ORM

Shipped · v0.3.0

The Sitecore Headless GraphQL ORM — strongly-typed, Synthesis-style item models over the Sitecore GraphQL Edge. Four focused packages, no third-party GraphQL dependency.

See Axlis.ORM

Axlis.Sitecore.Context

Shipped · v0.1.0

A thread-safe, per-request replacement for Sitecore.Context.Database, Sitecore.Context.Request, and HttpContext.Current.

See Axlis.Sitecore.Context

Axlis.Customizations

Shipped · v0.1.0

Sitecore Content Editor and Shell control customizations — starting with QueryableTreeList, a query-aware TreeList field.

See Axlis.Customizations

Where Axlis is going

A Sitecore ecosystem, one component at a time.

Three families shipped so far. Here's what's next.

  1. Shipped · v0.3.0

    Axlis.ORM

    The Sitecore Headless GraphQL ORM — typed templates, axes, caching, diagnostics and DI, across four packages.

  2. Shipped · v0.1.0

    Axlis.Sitecore.Context

    A thread-safe, per-request replacement for Sitecore.Context.Database and HttpContext.Current — for the multi-threaded scenarios where the ambient Sitecore statics fall short.

  3. Shipped · v0.1.0

    Axlis.Customizations

    Sitecore Content Editor and Shell control customizations, starting with QueryableTreeList.

  4. Planned

    Axlis.Diagnostics

    Enhanced diagnostics and monitoring for Sitecore applications, building on the diagnostics sink already in the ORM.

  5. Planned

    Axlis.Caching

    Advanced caching strategies for Sitecore data, beyond the stampede-safe item cache shipping today.

For early adopters

Be among the first to build on Axlis.

Star the repo, install the preview, and open a discussion. Your feedback shapes v1 and the components that follow.