Container
Run in your container environment with persistent storage.
For teams with deployment requirements
Run the TestifySec Platform in your environment as a container, single binary, VM image, or AWS Marketplace instance. Choose how it runs and where its data lives.
Choose your deployment format
Run in your container environment with persistent storage.
Run directly on a supported host.
Deploy an image into your virtual infrastructure.
Deploy in your AWS account through AWS Marketplace.
Explore AWS MarketplaceChoose the package that fits your environment. Confirm its supported runtime, image format, and release during your deployment review.
Deployment architecture
Run the core services together on one host. Connect developers and CI runners to your own Platform endpoint.
Your infrastructure
Single hostThe Platform, packaged for local operation.
Before you deploy
A practical checklist for your infrastructure and security teams.
A compatible container runtime, binary host, VM environment, or AWS account. The selected package determines its operating system and architecture requirements.
A durable, writable data directory for the database, evidence, and signing material. Plan capacity around evidence volume and retention.
A signed appliance license, an initial administrator, and your chosen login configuration. External identity providers are optional.
A stable hostname and certificate trusted by users and runners. Allow HTTPS access and the connections your selected integrations need.
Assign ownership for backups, restore tests, monitoring, updates, certificate renewal, and accurate system time.
Use your actual evidence volume, concurrent workflows, and retention period to size the host. Plan high availability separately from the single-host appliance.
Reference evaluation host
2 vCPU / 8 GiB RAM / 40 GiB disk
Ubuntu 24.04 LTS · Linux x86-64
Used for a documented evaluation workload. This is not a production minimum or a capacity guarantee. Size production with your workload.
Network planning
Local core services reduce external dependencies. Each integration still needs a deliberate network plan.
Keep internal ports private. Signing-service and metrics ports do not need to be open to users or CI runners.
Review each data path. Repositories, identity providers, object storage, email, and AI services may need additional network access. Inbound webhooks may also be required.
Your team operates
Host, network, data storage, access, monitoring, backups, recovery, and applying updates.
TestifySec provides
Licensed software, release packages, documentation, and support under your agreement.
Plan together
Capacity, availability, connected services, upgrade procedures, and acceptance criteria.
The packaged appliance runs as one process on one host, without built-in failover. Multi-replica deployments require a separately planned architecture.
Your next step
Bring one real workflow. We’ll work through the fit with your team.
Start with your challenge
Choose the problem you are solving. See where TestifySec fits and how to get started.
Require evidence that the checks ran before a push reaches your repository.
Protect your next pushPlatform teamsManage the gates across your repositories from one place.
Bring your gates togetherSecurity and assurance teamsConnect recovery tests and remediation checks to the controls they support.
Turn tests into evidenceTeams with deployment requirementsExplore the software appliance and plan for your data, network, and operating needs.
Explore the appliance