01The platform

What the agents
actually run on.

A multi-tenant control plane on Postgres, an orchestrator for long-running workflows, streaming chat, and workers for ingestion and deployment. Every write is idempotent and every consequential action is audited.

Request the architecture briefSee pricing
Live from a running instance
GET /health
{
  "status": "ok"
  "dbDriver": "pglite"
  "dbLatencyMs": 1
  "providers": {
    "model": "not configured"
    "esign": "stub"
    "payments": "stub"
    "storage": "local"
  }
  "standIns": [
    "database: embedded PGlite"
    "esign: stub"
    "payments: stub"
    "model provider: absent, rules-only classification"
  ]
}
02Capabilities

Eight moving parts, each with an owner.

“The AI does it” is not an answer a security review accepts. Every capability names the accountable agent and the endpoint it lives behind.

Chat-first intake

One question per turn, driven by what is still missing. Every extracted requirement cites the phrase it came from.

POST /intakes/:id/messages
ChiefManager™
Classification

Deterministic rules establish a floor and always persist; the model is merged additively above a confidence floor, and can never remove a signal the rules found.

POST /intakes/:id/classify
ChiefManager™
Prerequisite wizards

JSON Schema served from the backend so the form is generated once, and its answers feed pricing directly.

GET /schemas/cv_prereqs
ChiefManager™
Estimate engine

Published formula, integer cents, basis-point multipliers. Computes from stored requirements, no client-supplied amount.

POST /projects/:id/estimate
ChiefManager™
SOW generation

Thirteen fixed sections, versioned in object storage, issued for signature with signer tracking.

POST /projects/:id/contract
ChiefManager™
Payment gating

Card, ACH, wire or purchase order. Kickoff blocked in code until webhook-confirmed. Idempotent writes.

POST /projects/:id/checkout
ChiefManager™
Delivery orchestration

Repos, IaC and pipelines generated, then deployed to the target you specified. Acceptance suite before handover.

POST /projects/:id/kickoff
ChiefArchitect™
Telemetry & audit

Health, agent activity, spend and audit history from the moment the system is live. CSV and PDF export.

GET /projects/:id/telemetry
ChiefRelations™
03Where the weeks go

The delay is rarely the engineering.

Discovery, proposal writing and procurement consume the calendar before anyone writes code. That is the part the agents remove.

Conventional
Weeks 1-2Discovery calls
Weeks 3-4Proposal drafted by hand
Weeks 5-6Legal redlines, PO, countersignature
Week 7+Engineers pulled from other work
Here
MinutesChat intake, requirements extracted
MinutesFixed scope priced, drivers shown
Same daySOW issued, signed, payment cleared
ImmediatelyProvisioning begins
04Architecture

Built to survive a vendor risk review.

Postgres is the system of record. Redis carries cache and locks. Artifacts are versioned in object storage. Chat streams over SSE. Everything is packaged for Docker and Kubernetes, including offline bundles.

Specification
Model layerAgnostic, swappable per task
System of recordPostgreSQL
Cache & locksRedis
ArtifactsObject storage, versioned
Chat transportSSE streaming
PackagingDocker / Kubernetes
Availability target99.9% control plane
Chat latencyP95 < 2s to first token
Scale10k concurrent sessions
05Security posture

Baseline, not roadmap.

SSO & RBAC

SAML and OIDC against your identity provider, with role-based access and workspace separation per org.

Audit logging

Every login, connector grant, signature, payment and deployment action is recorded and exportable.

Encryption

Encrypted at rest across database and object storage, and in transit over TLS throughout.

Token vault

Connector credentials are held encrypted under KMS and scoped per organisation and project.

Data residency

Configurable retention per organisation. Delete connectors and derived indexes on request.

Deployment choice

Cloud, private VPC, on-premise or edge. Docker and Kubernetes first, air-gapped supported.

POST/webhooks/payment401
unsigned payload rejected
{
  "error": {
    "code": "UNAUTHORIZED"
    "message": "Invalid webhook signature"
    "correlationId": "ad7d4b51-35a5-4d68-8ec5-daa21e593fca"
  }
}

Put it through your security review.

We will walk your team through the architecture, the audit model and the deployment options before you commit to anything.

Request the briefWorked scenarios