Skip to content
Security

Your data never
leaves your network.

TwinCommit is self-hosted software. It runs next to your databases, uses the minimum privileges each platform needs, and gives you control over what is replicated and who can operate it.

Self-hosted, always

TwinCommit runs inside your network. Replicated data never passes through TwinCommit infrastructure or any third-party cloud.

Least-privilege by design

twincommit check lists exactly which privileges each source and target needs, and nothing more.

Secrets stay in your vault

Pipeline files reference ${ENV} variables, so credentials come from Kubernetes secrets, Vault or your CI system and never from the YAML.

Encrypted in transit

TLS to every source and target that supports it, and mTLS for the Spark change-feed endpoint.

Column exclusion

exclude_columns keeps sensitive columns (card numbers, national IDs) from ever leaving the source host.

Safe AI operations

The MCP server is read-only by default, redacts row values and audit-logs every tool call.

Signed releases

Every binary and container image is signed with Sigstore cosign and ships with an SBOM.

Spill-file hygiene

Spilled transactions are written with 0600 permissions and deleted as soon as they are applied.

Report a vulnerability through our contact form (choose “Technical question” and start with “SECURITY”).

Replicate your first table in five minutes.

Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.