AI and agents

AI, in the places it actually pays.

Anyone can buy the same model you can. The work is connecting it to your systems, setting what it may do, and showing where an answer came from.

Shipped
Platform · connectors · agents
Hosting
Cloud · on-prem · air-gapped
Foundation
Our own open-source stack
01 · ASKEDQUESTION02 · READYOUR DOCUMENTSthe passage usedread-onlyYOUR SYSTEMSERPCRMDMS03 · ANSWEREDMODELanyone can buy itswappable04 · RETURNEDANSWERfrom your systemfrom your documentEvery line points back at where it came from
Question → your documents → model → answer, every claim tetheredThe model is the smallest part

What we build

Eight kinds of build, one foundation.

01

Intelligent platform

One place your team works: projects, channels, saved sessions.

Desktop and browser · one codebase

02

An assistant

Answers from your systems, not the open web.

Internal or customer-facing

03

Searchable documents

Your documents, searchable by meaning rather than keyword.

Vector search · OCR · citations

04

Connectors to what you run

The systems you already run, opened up for an assistant to query.

MCP · read-only by default

05

Automation and workflow

Long processes that survive a crash or a restart.

Durable · event-driven

06

Analysis and forecast

Charts and forecasts from live data, not last month’s export.

Generated from live data

07

Harness engineering

The rules your developers’ AI has to work inside.

Per codebase

08

Training your team

Workshops, from how a model works to running agents safely.

Half day to two days

01 · INPUTSCREENSHOTvision · OCR02 · EXTRACTEDjob id · program · timestampvalidated against a schema03 · SYSTEM SNAPSHOTREAD-ONLY · COMPILEDserved over MCP as a toolnetwork shareslog locationsscheduled tasksapplications → sourcecallable ERP programsqueryable · no writes backno documentation existed04 · CORRELATEDprogram → task → interfacesacross sources that never met05 · RETURNEDDIAGNOSIStimestampedevery claim linkedtool calls on the recorda human still decidesAny input · answered from your systems · every claim traced
Screenshot in, cited answer outRead-only throughout

In production

No internet, no documentation, one engineer.

An industrial group whose machines cannot reach the internet, and no record of what runs where.

We built a searchable, read-only picture of everything they run, on models hosted on their own machines. Nothing leaves the site.

A technician pastes a screenshot of an error. The answer comes back with a link to each thing it checked.

Placement

Where it belongs, and where it does not.

Machines and devices

Runs on the device itself: transcription, reading images, sorting.

Quantised local models

NotA cloud call from a device that keeps losing signal.

The software you already run

An assistant that queries your systems and shows what it read.

MCP servers over existing systems

NotPasting a database layout into a prompt and hoping.

Moving data between systems

Proposing how two systems’ fields line up, and where they clash.

Structured output · typed contract

NotLetting it write into your ERP unsupervised.

Services and APIs

What the model returns is checked at the door, like any outside input.

JSON Schema · OpenAPI 3.1

NotTrusting the model’s text because it looked right.

Reporting and forecasts

Forecasts, unusual patterns and charts from your own data.

Query shown · result reproducible

NotA number nobody can trace back to a query.

Your development team

Agents inside set limits, every change checked before it lands.

Agent Skills · fitness gates

NotAutocomplete pointed at production and called a strategy.

Keeping it running

Working out what broke, from a map of what you run.

Per-call audit · citations · SSO

NotAn unaudited assistant holding production passwords.

The foundation

We already own the layer underneath.

Most of what an AI product costs is plumbing every project rebuilds. Ours is already built.

L1 · Runtime
Nothing reaches a file or the network without an explicit grant.secure by default · no node_modules · single binary
L2 · Framework
Client, server, validation and documentation derive from one definition, so an integration error is a compile error.typed contracts · plugins · AI stack · traces
L3 · Product
The part that is specific to your business.your domain · and nothing else

We publish that middle layer as NetScript, openly licensed.

Without a frameworkWith oursALL OF ITprovider adaptersagent looptool protocolstreamingworkersdurable workflowsauthtracescontractspermissionspackagingevent streamscost metering…and your domain,somewhere in thereL3 · PRODUCTyour domain · and nothing elseL2 · FRAMEWORKtyped contractspluginsAI stacktracesL1 · RUNTIMEsecure by defaultno node_modulessingle binaryWork moves down into the layer we maintain
Same total height, different economicsThe top band is what you pay for

Harness · the run loop

Five steps, and one way back.

Work that fails a check comes back.

01BOOTSTRAP02DESIGN03EXECUTE04GATE05EVALUATEFailRejectedEighteen checks · one route back, into execute
A failed check and a rejected review come back to the same step

Read the rules before starting

The agent reads the architecture rules and the known problems first.

Governance

What a security review actually asks.

Pilots stall at the same six questions every time.

Model access
One gateway, keys held server-side, bring-your-own-key per team.
Data boundary
One component talks to the model provider. Nothing else does.
Identity
Single sign-on over OIDC and existing group membership.
Audit
Every conversation kept as the record, including what was read.
Cost
Tokens metered per channel, provider and model.
Sovereignty
Swiss or EU hosting, on-premises, or fully air-gapped.
AI plane · egress only if chosenDIRECT PROVIDERnamed vendor · own keyAGGREGATORone key · hundreds of modelsPremises boundaryPROVIDER ADAPTERswappable per data classLOCAL MODELzero egress · air-gap capableData plane · stays on the LANCHANNEL STOREShistoryvectorsKNOWLEDGE BASEdocumentscitationsCONNECTORSread-onlyover MCPAUDITall tool callswhat was readTwo providers reachable. One component may reach them.
One boundary, one crossingLocal models cross nothing

Next step

Start with the problem, not the model.

Tell us which job you want AI to do, and which systems it would read.