Integration and execution
Connect the systems your team ships
- Native Go verification
- Rust, C++ and Java process adapters
- Instrumented execution for Go and Java runtimes
- Container, Model and Instrumented execution paths
Promtact Enterprise
Run deterministic verification on your infrastructure.
Run deterministic verification inside your own infrastructure, from a single host to Kubernetes, with controlled execution and replayable results.
Turn difficult failures into tests your team can run, share and replay before the next change ships.
Enterprise features
The complete controlled operating path
Enterprise combines language integration, controlled execution, replay and day-two operations around the deterministic engine.
Delivery and security
Keep deployment inside a controlled boundary
- Single-host and Kubernetes installation
- Provider-neutral and offline delivery
- TLS, signed artifacts, provenance and SPDX SBOM
- Role-bound access, OIDC mapping and audit records
Operations and replay
Keep failures useful after the first run
- PostgreSQL-backed job history and persistent runner journal
- Share and replay a stored failure
- Verify a candidate fix against the same recorded test
- Upgrade, rollback, backup, restore and disaster recovery
Enterprise security review
Answers for the first security questionnaire
The current boundary states what is implemented, qualified and still pending rather than hiding those distinctions behind a generic security claim.
Identity and authorization
Viewer, Editor and Admin roles protect organization and project operations. Tokens are stored only as SHA-256 digests, and OIDC can map users into the appropriate organization.
Audit and retention
Successful mutations create append-only audit events. Project policy, audit export and retention controls keep operational history available for review.
Network and privilege boundary
Single-host deployments isolate privileged execution in a separate agent. Kubernetes deployments use a project-scoped, unprivileged runner with restricted access to its execution namespace.
Supply-chain controls
Release signatures, canonical manifests, provenance and an SPDX SBOM accompany release artifacts. CI adds static analysis, fuzzing and container scanning.
Independent assessment status
An independent security review is planned. No completed external audit or certification is currently claimed.
Review the public security policyCommercial stage
Design-partner evaluations are the current entry point.
No customer case study is published yet. Early engagements begin with one consequential correctness boundary and produce a clear integration, deployment and operating scope.
PricingScoped per engagement
Starting pointOne system and failure mode
OutputRepeatable checks and bounded evidence
Adoption path
Start with one consequential failure mode
Keep the first engagement narrow enough to prove value and concrete enough to become an engineering control.
- 01
Define the boundary
Name the protocol behavior, failure mode and property that cannot be violated.
- 02
Connect the system
Select the qualified integration or execution path that matches the target boundary.
- 03
Install and operate
Deploy the self-hosted distribution and connect it to the team's release workflow.
- 04
Make it repeatable
Place the scenario and its evidence into the team's release and review workflow.
Deployment
Run it where your system already lives
Promtact Enterprise supports a compact single-host installation and a Kubernetes deployment with separate control and execution boundaries.
The Kubernetes path uses PostgreSQL for durable state, a persistent runner journal and project-scoped execution. Delivery remains provider-neutral and can operate without a hosted Promtact control plane.
- Deployment
- Single host or Kubernetes
- State
- PostgreSQL
- Execution
- Project-scoped runner
- Cloud dependency
- None required
- Operation
- Self-hosted
Support model
Engineering support with explicit scope
Evaluation, adapter work and operating support are scoped around the system and correctness boundary being verified.
Evaluation
Determine whether Promtact fits the target protocol and failure mode.
Integration
Connect the supported adapter or runtime boundary required by the target system.
Release workflow
Connect repeatable checks and results to the team's release decision.
Operations
Establish installation, diagnostics, upgrade, rollback and recovery procedures.
Evidence before claims
Every conclusion has a boundary.
Promtact records what was exercised, against which source identity, and what the result establishes. It does not turn a bounded campaign into an unlimited reliability promise.
Evaluation
Bring the system boundary, not a generic sales brief.
Tell us the implementation language, deployment environment, failure mode and property that matters. We will determine the smallest credible evaluation scope.