Skip to main content
Engagement

How We Engage

Bespoke deployments, productized apps, and licensing. Three engagement models for different stages of integration.

/ Composability

Works with what you already use.

The teams we work with have already invested in foundational models, vertical AI products, and internal tooling. Our technology is built to compose with all of it — that's a property of the underlying system, not an integration feature we bolted on.

In practice, that means we sit alongside the systems your people already trust, contribute reasoning and verification where it matters most, and produce a complete audit trail across the entire decision path — including the parts we didn't author.

FOUNDATION
OpenAI · Anthropic · Google · open weights
VERTICAL AI
Whatever your domain has standardized on
YOUR STACK
Your data, your IdP, your audit, your perimeter
DEPLOYMENT
Owned · Controlled · Governed
/ Engagement

Briefing to deployment.

01

Briefing

We start with a closed-door technical and operational briefing — your domain, your data posture, the decisions that have to be defensible, and the constraints we have to live inside.

02

Bespoke design

We design a reasoning system fit to your workflow — not a generic agent and not a wrapper. Architecture, model selection, verification rules, and authority structure are all worked out for your domain.

03

Direct deployment

We deploy directly to you — Owned appliance, Controlled VPC, or Governed managed cloud. Your data does not leave your perimeter to reach our substrate. See /sovereignty for the full posture map.

04

Operate and evolve

We run alongside your teams: tuning, expanding scope, integrating new sources and new agents, and keeping the audit and authority surface clean as the system grows.

/ Phase 03 — Direct deployment

Three postures. One substrate. Pick the one that matches your boundary.

Your data does not leave your perimeter to reach our substrate. Same audit log, same agent runtime, same SDK — whether the reasoning runs on a box in your server room, a VPC in your cloud account, or a 1331-managed tenant.

Full sovereignty posture map
/ Commercial structure

How engagements are priced.

Bespoke design

Fixed-scope design and integration fee. Scoped from the briefing, paid in milestones tied to deployment gates.

Substrate license

Annual license per posture — Owned (per appliance), Controlled (per VPC), or Governed (per tenant). Hardware sold at cost for Owned.

Run-rate

Operate-and-evolve retainer covering tuning, scope expansion, integration of new sources and agents, and ongoing audit hygiene.

1331 does not publish list prices. Numbers are produced from the briefing — once the posture, scope, and audit obligations are known, the commercial structure follows from them in one page.

/ Licensing

Technology Licensing

For organizations that want to integrate 1331 technology into their own products and platforms, we offer licensing arrangements tailored to your deployment model, data environment, and commercial structure. Licensing conversations begin with a technical briefing under NDA.

Request a Licensing Briefing
Request a BriefingDomains we serve