Book a Demo Talk to Sales

Developers

Extend and build
on the platform

The defaults will not fit every domain. Where they do not, the extension points are the same ones the built in features are written against.

Start free Read the Docs
Your module, plugged into the platform The platform as a 3 by 3 block of modules: search, graph, agents, enrichment, API, auth, audit and connectors, with one slot open. Your own module, a warranty check, steps into it as a type, an endpoint, an interface or an agent tool. 01Search02GraphSLOT04Agents05Enrich06API07Auth08Audit09ConnectYOURSWarrantycheckPLUGS IN ASTypesEndpointsInterfacesAgent tools
Your code, inside: Custom types, Custom endpoints, Custom interfaces Custom types: Model what your domain actually has. Custom endpoints: Your logic, exposed as an API. Custom interfaces: Domain applications, served directly. All inside one your code, inside. 01 Custom types Model what your domain actually has 02 Custom endpoints Your logic, exposed as an API 03 Custom interfaces Domain applications, served directly

Capabilities

Your logic and your UI, inside the platform

Extension is not a plugin system bolted to the side; it is how the platform is built.

Custom entity types

Model the things your domain has, with the fields and relationships they really carry.

Custom endpoints

Expose your own logic over the graph as an API, with the same auth and audit as everything else.

Custom interfaces

Build a domain-specific application that the deployment serves, rather than a separate app to host.

Pipeline steps

Your own enrichment and processing, as first-class steps.

Agent tools

Register your functions so agents can call them.

Same permissions

Everything you add inherits the access model rather than needing its own.

Questions for developers

The things worth asking first

What language do I write extensions in?

C#, for endpoints, AI tools, scheduled tasks, code indexes and connectors, with the same types Studio uses. Connectors can also be written in Python.

Do extensions survive upgrades?

Extensions are kept as source and compiled by Studio, so an upgrade compiles them against the new version and a break shows as a compile error, not a silent failure. Stay on the documented surface (Graph, ChatAI, AgentAI) and it holds.

Can I replace the built in UI?

Yes. Push your own front end, written in C#, to Studio over git. It compiles each commit to a preview, and you promote the one you want to live.

Your data. Your infrastructure.

Build what the defaults do not cover

Book a Demo Talk to Sales