Promenaut joins forces with HSBC as strategic investor and design partner.Read More
Layer 9 · The foundation
Where it runs, deploys, scales, recovers and is operated, and how Promenaut builds and ships it.
What it is not. Not a hosted black box. The platform can run in the client's own cloud account, and each release is rehearsed through the client's own deployment pipeline.
01
A client can bootstrap, deploy, upgrade, verify and roll back the platform in its own AWS account with a shipped kit, including a full bundle carrying the images and signed modules for an environment without outbound access.
02
Each stable baked release is deployed end to end through the client's own pipeline script, vendored with a checksum guard, in an isolated account, verified, and then torn down.
03
The database, both Redis clusters, shared file storage and the object store are encrypted at rest.
How the services, queues, event bus, database and file storage fit together, and how the schema changes safely
Network isolation, encryption, credentials, certificate trust and rate limits across the hosting estate
Scaling on demand, pacing model providers, and picking up work that failed or stalled
How releases are cut, versioned, identified, scanned and promoted
Putting a release into an environment, client or internal, checking it first and rolling it back
Seeing what the running platform is doing and acting on it: console, tracing, alarms and alerts
How changes are made, checked, reviewed and merged before they reach a release
Bring a real process. We'll show what your first agentic workflow looks like on the platform.
Promenaut