Engineering Trust at Every Layer.
Most "trust" claims in SaaS are policy documents. Aeion's trust is enforced in the architecture — kernel tenant isolation, type-system-level cross-tenant prevention, immutable audit signing, deterministic compliance enforcement, honest adapter no-ops. Each page below documents the engineering choice that makes a given guarantee real, with code-level references and the failure modes the choice prevents.
Security, Compliance & Access (3 deep-dives)
GDPR Privacy Architecture
Article 32 controls implemented at the product surface. Right-to-erasure cascade across collections. Data residency selection per tenant. DSR workflow audit-trailed. Lawful basis tracking. EU-region hosting and AI inference. Full deep
Learn morePCI-DSS Tokenization
Stripe / Adyen tokenization at every payment path. We never store PANs. Audit log on every charge with payment-path attribution. SAQ-A scope; processor owns the PCI environment. Full deep
Learn moreEnterprise RBAC
Multi-factor auth, SSO via SAML/OIDC, field-level permissions, session expiry policies, IP allowlisting, admin-impersonation audit. Zero-trust architecture — every API call resolves user → tenant → permissions before the handler executes. Full deep
Learn moreCore Engineering Foundations (3 deep-dives)
Database Wrapper
Drizzle ORM proxy with kernel-level tenant scoping. The tenant predicate is auto-injected into every query at the wrapper level and cross-tenant queries are refused at runtime; the type system separates the tenant-scoped `db` client from the cross-tenant `sysDb` client so module code can't reach for `sysDb` by accident. Temporal time-travel via reverse JSON Patches. The tenant boundary is enforced below business logic where it cannot be bypassed. Full deep
Learn moreGlobal API & BaaS Protocol
Auto-CRUD REST on every collection, generated from Drizzle schema. Standard envelope, sparse fieldsets, cursor pagination, depth-controlled population. The BaaS surface that lets every module compose without an integration layer. Full deep
Learn moreUniversal AST Engine
Visual code compilation across the platform — Blueprint workflows, Spatial scenes, Motion Studio compositions, AI tool definitions all share a common AST representation that compiles to typed runtime artifacts. Full deep
Learn moreSpatial & Generative Computing (2 deep-dives)
Character Engine
Next-generation cognitive architecture for digital humans. Personality + memory + skill mechanics + social systems + advanced character geometry. The engineering behind autonomous, persistent NPCs in spatial scenes and AI-customer-facing avatars. Full deep
Learn moreWorld Capture
Enterprise photogrammetry and Gaussian splat pipelines. Drone capture orchestration, multi-provider 3D scanning (Polycam, Luma, Meshy, Tripo3D), mesh optimization, AR-ready asset output. The capture-to-render pipeline for spatial-computing deployments. Full deep
Learn moreCross-Cutting Reference (3 catalogs)
Collections Reference
22 field types across 6 categories. The collection schema that defines every business object. Auto-CRUD, validation, access control, indexing, and field-level encryption all derive from this contract.
Learn moreEvents Catalog
900+ typed platform events on one bus. Standard envelope with `tenantId`, `traceId`, `userId`, `payload`. The event surface that lets modules compose without point-to-point integration.
Learn moreExternal Adapters
The Honesty Rule for third-party integration. Every adapter to a real-world device, API, or provider returns `transmittedToProvider: false` with a machine-readable reason when no real call was made. No fake successes. Full deep
Learn moreWhy Architecture Pages Matter
SaaS architecture deep-dives usually live in three places: a 4-page whitepaper marketing PDF, an "we'll talk under NDA" sales gate, or buried in source-code documentation only employees read. None of those serve an engineering-team evaluation. Aeion's architecture pages are public, technically detailed, and reviewable — and Enterprise customers under NDA can request the code-level cross-references that go deeper than what we publish openly.
What's Missing From This Hub
The architecture surface is one of the highest-investment areas of Aeion documentation, but it's not complete yet. Pages we're prioritizing for the next wave:
Frequently Asked Questions
No. The architecture pages document specific engineering choices, code-level references, and failure modes the choices prevent. The acid test: an engineering team should be able to evaluate Aeion's posture from these pages without an NDA. If a page reads like marketing, tell us and we'll rewrite it.
Bandwidth. Architecture deep-dives are the most time-consuming pages to write because they need engineering review and code references. We prioritize by inbound demand — when an enterprise evaluator asks for a specific architecture page, we put it next in the queue.
Enterprise customers get architecture-team office hours and pre-publication review of architecture documentation in scope. Talk to sales.
Aeion is closed-source, but enterprise customers can request a source-code review under NDA as part of due diligence. The architecture pages give you the surface area to know what to ask for; the review fills in the implementation details.
Aeion's controls are mapped to the SOC 2 Trust Services Criteria today (see our SOC 2 readiness framework), with a formal Type II audit by an accredited CPA firm as our next planned compliance investment — plus ongoing internal red-team review of new features before they ship. See /trust for the full security posture and current audit status.
Tell us. The architecture pages are the source of truth — they're code-referenced and reviewable. If a marketing page makes a claim the architecture doesn't back up, the marketing page is wrong and we'll fix it.