Offerings.
Four ways to put the stack to work. Each stands on its own, and each builds on the one before it. The scale of buying it, with the ownership of building it.
Sovereign inference
The full stack, from AI models to the serving runtime, deployed inside your network. It runs on your GPUs or your private cloud, behind your firewall, wired into your identity and logging.
On your own hardware the work compounds into something the company keeps, instead of a rental that leaves nothing behind.
We own the models and the serving rather than reselling somebody else's API. That is the only reason it can run with the internet unplugged.
- deployment
- on-prem / private VPC
- models
- ASR · TTS · LM
- interfaces
- REST + streaming
- data boundary
- nothing leaves
- updates
- on your schedule
- logging
- local, audit-ready
- stands on
- your hardware
Loom · retrieval with sources
Tickets, wikis, repositories and years of tribal knowledge, made searchable. Vector, keyword and relational indexes work together, so an answer comes back with its source instead of a plausible guess.
Access controls travel with the knowledge. Nothing surfaces for someone who could not already have seen it. You can ask the company a question about itself and get an answer you could show an auditor.
- indexes
- vector · keyword · relational
- answers
- linked source
- access
- controls travel with it
- sources
- tickets · wikis · repos
- audit
- answers that can be shown to an auditor
- stands on
- sovereign inference
Weaver · execution with judgment
Takes an objective, plans the work, and executes inside a hardened sandbox without stopping for permission at every step. It checks what it is allowed to touch, whether the action fits policy.
- input
- an objective
- execution
- hardened sandbox
- before acting
- policy + precedent
- permissions
- set by the sandbox
- judgment
- checked against Loom
- stands on
- loom
Aural · AI and human agents
Voice agents and WhatsApp agents with human teams behind them, for support and sales that scale conversations without growing headcount. Every interaction is logged, with a person able to step in.
Aural points the same stack at where the work actually happens: a phone call and a message thread. It runs on speech models that survive a real Indian phone line and a speaker who changes language halfway through a sentence.
Its own product, its own team, running as a managed service by default. When a customer needs it inside their own machines, the stack above enables it.
- channels
- voice · WhatsApp
- model
- managed service
- oversight
- human in the loop
- audit
- immutable trail
- status
- in production
- stands on
- the whole stack