Book a Demo Talk to Sales

Developers

Full developer
toolkit, built in

This is code you should be able to review, version and test like the rest of your codebase, not configuration hidden inside a console.

Start free Book a Demo
A query in code, and the plan it ran Four lines of C# search for a hydraulic leak, traverse to the supplier and ask for an explanation. Below, the query plan: permissions, keyword, vector, graph walk, then fuse and rank, 18 milliseconds in all. QUERY.CS1var hits = await graph2 .Search("hydraulic leak")3 .Traverse("SuppliedBy")4 .Explain();QUERY PLAN · 18MSPermissions2msKeyword4msVector7msGraph walk3msFuse · rank2ms
Build and operate: Build, Debug, Operate Build: C# SDKs, REST APIs, the build environment. Debug: Inspect queries, retrieval and agent traces. Operate: Deploy, monitor and roll forward. All inside one build and operate. 01 Build C# SDKs, REST APIs, the build environment 02 Debug Inspect queries, retrieval and agent traces 03 Operate Deploy, monitor and roll forward

Capabilities

Build, manage and deploy from one place

Everything needed to develop, debug and operate a Studio deployment.

C# SDKs

A typed client for the graph, retrieval and agents, in the language the runtime is built in.

REST APIs

The same surface the built in interface uses, so nothing is reserved for the vendor.

Build environment

Develop and test against a real graph on your own machine, on the free developer install.

Query inspection

See how a query was planned and why a result ranked where it did.

Versioned configuration

Schema and pipelines as code, reviewable in a pull request.

Operational visibility

What is syncing, what is slow, and what failed overnight.

Questions for developers

The things worth asking first

Do I need a license to develop?

No. Without a license key Studio runs with every feature on, for up to ten test users, with no time limit for development use.

Is the API the same one the UI uses?

No, and on purpose. The UI talks to its own session API. Your code uses the Library API with a token you can revoke, or the REST endpoints you write in C# inside Studio.

Can configuration live in git?

Yes. Studio commits every configuration change to a git repository and can push it to your remote. Schemas, endpoints, AI tools, agents and tasks are files you can review, and you import them back as a bundle or from the command line.

Your data. Your infrastructure.

Build it on your own machine first

Book a Demo Talk to Sales