The core is done. Build only what is yours.
A platform on Nexus is the shared core plus a domain pack. The pack holds the words, rules, screens and checks of one industry. Our teams build packs this way, and so can yours.
Five parts. The rest comes with Nexus.
Chat, notebooks, the switchboard, records and permissions are already there. A pack adds only what makes an industry different.
- A knowledge model
The things an industry talks about, such as claims, loans, missions or matters, and how they connect.
- Lenses
What each role sees. A claims handler, a fraud analyst and an auditor look at the same claim through different lenses.
- A manifest and permissions
What the pack may reach, which engines it uses, and what it must ask a person before doing.
- Rules and checks
The rules of the industry, mapped to the evidence that answers them.
- Decision models
Small models trained on your own sealed records for the judgements the pack makes most often.
Built, tried and reviewed. Then released.
Every pack goes through the same path, with sample data at each step and a review before anything reaches real people.
Manifest and permissions
The manifest says what the pack may reach and what it must ask first. Nexus enforces it, so a pack cannot quietly do more than it said.
Try it as the person who will use it
Preview a lens as a real role before anyone uses it. Your own permissions do not leak into the preview, so you see exactly what they will see.
Sample data for testing
Every pack ships with realistic sample data, so it can be tried, demonstrated and tested without touching real records.
Release review
Before release, a person reviews what changed: new permissions, new rules and test results. Nothing reaches users without that sign-off.
Tools for the people who build packs.
The developer kit includes the SDK, a command-line tool, connectors for your own systems and AI tools, and a place to see each pack's logs and measures.
- SDK for packs, lenses and connectors
- Agent passports built into the SDK
- Environments from your laptop to production
- Logs and measures for each pack
Developer documentation is available to signed-in partners and customers. Sign in or ask for access.
Three ways to get a platform
- Use ours
Ten industry packs, ready to turn on.
- Build with us
Our team builds your pack with your experts.
- Build your own
Your developers use the kit, and we review the release.
About building on Nexus.
How long does a new pack take?
Weeks, not years, because the core is already built. The time goes into the knowledge model, the lenses and the rules, with your experts in the room.
Can a pack call our own systems?
Yes, through connectors listed in its manifest. Each connection is checked on every call, and a connector that would send data somewhere your rules forbid is refused.
Who owns a pack we build?
You do. Packs you build stay yours. We agree the details in the contract before work starts.
Go deeper
Bring the process. We will sketch the pack.
One working session with your experts is enough to outline the knowledge model, the lenses and the rules.