Architecture
Our engineering principles, plainly stated.
This isn't a logo list of the tools we use. Every technical claim on this page is clearly labeled with where it actually stands — in production, in active development, or still a design principle.
Three labels, one rule: no overstating.
Every item below carries one of these three labels. If a technology is mentioned here, we don't hide how mature it actually is today.
- In production
- It's genuinely running today and relied upon.
- In active development
- It's being built right now; not yet complete or used everywhere.
- Design principle
- A direction we believe in and build toward; not yet a shipped guarantee.
Nine areas, one discipline.
We describe our architecture across nine areas. Names are deliberately kept general — capability layers, not internal project code names.
Contract layer
Technical agreements between components are kept as readable documents, not as code.
- Design principle
Contracts between components are written as versioned, machine-readable documents (Markdown + JSON Schema) with explicit acceptance criteria.
Agent runtime
What an agent can do is bounded by defined limits, not open-ended.
- In active development
Agents operate with a scoped, explicit set of tools rather than open-ended system access.
- Design principle
Execution runs in isolated sessions, with routing between components handled by defined rules.
Governance
Critical actions don't happen in a vacuum — they pass through a defined approval and record layer.
- In active development
Every cross-component request passes through a central approval layer before it is acted on.
- In active development
Approval and rejection decisions are written to an immutable record for later review.
- In active development
Critical or irreversible actions pass through a separate human-approval step.
Knowledge
Decisions and context aren't left to survive only in chat history.
- In active development
A hybrid retrieval approach — combining vector search, graph relationships, and keyword (BM25) search — is being developed as a shared knowledge service.
- In active development
Decision history and architectural context are being captured as structured memory.
Verification
There's a defined verification expectation before a change counts as "done".
- Design principle
Changes are expected to pass deterministic, repeatable tests before they're considered complete.
- Design principle
The session that writes a change and the session that reviews it are kept separate.
- Design principle
Hidden or "golden" test sets are used only where a project genuinely relies on them — never presented as a universal practice.
Platform
Production workloads rest on a shared platform layer, not a single server.
- In production
Backend services are built in Go, with TypeScript/React where a user interface is needed.
- In production
PostgreSQL is the standard data store; production workloads run on Kubernetes.
- In active development
A shared messaging and observability layer is being developed — not yet used the same way across every product.
Deployment choices
Where you run isn't forced into a single mold.
- Design principle
UAIS products are designed to support different deployment models, including private cloud, self-hosted environments, and local inference. Whether a given product actually supports a specific model today is stated on that product's own page, not here.
Security posture
Access is narrow by default; broad access is the exception, not the norm.
- Design principle
Access is scoped to least privilege by default; broad standing access is treated as an exception, not the norm.
- Design principle
Tenant and workspace boundaries are designed as hard limits, not soft conventions.
- Design principle
Credentials and keys are managed through a single, auditable path rather than duplicated across services.
- Design principle
Data is treated as something that's expected to be encrypted and backed up as a matter of course.
Want a deeper technical conversation about our architecture?
We're happy to walk through what's behind each label on this page, and what it means for a specific product.
Request a technical call