Private tenancy.
Deployment lands in your cloud account — typically AWS Bedrock under your own agreement — so the data plane is yours by construction, not by policy.
Layer 01 — The ArchitectureQ3 2026
Foundation.
Tenancy, identity, isolation, and the infrastructure primitives every layer above depends on. The AI runs in your cloud, on your terms, with no shared boundary to ours.
Foundation is Layer 1 of the ism3 stack. Tenancy, identity, isolation, infrastructure primitives. The AI runs in the client's cloud, on the client's terms, with no shared boundary to ours.
Every ism3 engagement starts at the bottom of the stack. Layer 1 establishes where the system lives — your cloud account, your network boundary, your keys — before any model is selected or any document is indexed. The layers above inherit whatever the foundation gets wrong, which is why we refuse to treat tenancy as a deployment detail.
The commitment is structural rather than contractual: client data, query logs, and retrieval indices stay inside your tenancy. ism3 operates the system through scoped, auditable access — we run the infrastructure, and you retain the boundary.
Inside Layer 1.
Identity and access.
Who can invoke which model, read which index, and reach which surface is defined at the foundation and enforced by every layer above it.
Isolation boundaries.
No shared compute, no shared indices, no cross-tenant residue. The boundary between your environment and ours is explicit and inspectable.
Infrastructure primitives.
Networking, storage, secrets, and logging baselines that Layers 2 through 5 build on without re-deciding them per project.
Reference architecture
Whitepaper — Q3 2026.
The Layer 1 whitepaper will document the tenancy model, the identity and isolation architecture, and the infrastructure baselines an ism3 deployment establishes before anything above it ships.
The bottom of the stackEverything above inherits this boundary
Above — Layer 02OrchestrationFAQ
Layer 1, answered.
In your tenancy — typically AWS under your own account. ism3 designs and operates the system; the cloud agreement, the data, and the boundary remain yours.
Access is scoped to the engagement and auditable end-to-end. Operating the system does not mean owning it — every action we take is attributable and reviewable.
The foundation is designed for the layers above it, but engagements are scoped to what you need. Each one begins with a workflow inventory, and the architecture recommendation follows from that — not the other way around.