Your AWS environment. Your cyber DNA.
The customer-hosted container model keeps organisational state in the buyer's environment.
A contract container model.
The architecture is designed for AWS Marketplace contract distribution. Licensing identity is baked into the published container; buyers do not select a runtime flag to disable it. Licensing is checked before readiness and monitored while the service runs.
This page is not a subscription offer. No live Marketplace product identifier, approved listing, price, or universal deployment availability is asserted. Ask the team for current availability, an approved offer, and the supported image digest before purchasing or deploying.
Know what you are deploying.
The buyer package targets private application and worker tasks, authoritative PostgreSQL, encrypted secrets and evidence storage, logging, and controlled ingress. Terraform, CloudFormation, and EKS/Helm paths have different prerequisites and responsibility boundaries.
A successful launch needs more than a green health page: prove licensing, database connectivity, durable observation write/read, restart persistence, and the supported synthetic organism journey. Keep deployment and teardown scoped to the approved AWS account and region.
Prepare for an evidence-led evaluation.
Bring your intended AWS region, network topology, identity provider, data-handling requirements, model destination, and initial AWS/GitHub scope. The team can identify which capabilities are ready for evaluation and which require additional integration work.
Do not paste cloud credentials, Marketplace entitlements, or customer telemetry into a public repository. The public deployment surface is separate from private application source and does not expose customer-specific configuration.
Confirm current availability.
Request the current offer, supported image, and evaluation prerequisites. This site is not a Marketplace listing.
Ask about Marketplace readiness