d-stack Native

Peace of mind, deployed.

Trustless on first use

Traditional replication means trusting every node. TOFU inverts this: d-stack decrypts in TEE, other servers replicate encrypted via SHOYU. Your swarm grows, your trust boundary doesn't.

Download Coming Soon
🧈

Encryption at the source.
Replication everywhere.

01
πŸ”

Row-Level Encryption

Data encrypted before it touches Postgres. Your database stores ciphertext. Replicas sync encrypted WAL. Only TEE decrypts on read.

02
πŸ“‘

WAL Streaming via SHOYU

Mutable soy pointers track the WAL head. Replicas download segments and replay locally. Always encrypted at rest.

03
⚑

Automatic Failover

Lease-based leader election. If d-stack goes down, a new primary claims leadership. Epoch fencing prevents split-brain.

04
πŸ”‘

Key Rotation & Revocation

Remove a node by rotating the data key. New key sealed only to remaining members. No re-encryption of existing data required.

05
✍️

Row Signatures

Optional Ed25519 signature per row. Untrusted replicas can store data but can't forge it. Write authorization at the row level.

06
πŸ”€

Hybrid Clusters

Mix TEE nodes (d-stack) with standard servers. d-stack decrypts and writes. Standard nodes replicate and seed. Same swarm, different trust levels.

Your data's last moment of clarity
is inside the TEE.

01

Your app sends a write

Standard Postgres query hits your d-stack node.

02

d-stack encrypts at row level

XChaCha20-Poly1305 encryption before data touches Postgres. Database stores only ciphertext.

03

Encrypted WAL published via SHOYU

Mutable soy pointer updated. WAL segments available to swarm.

04

Replicas sync and replay

Download WAL via SHOYU. Replay to local Postgres. Data stays encrypted.

05

Replicas seed, can't read

Column values sealed. Replicas blind. Your meaning stays in TEE.

πŸ’» Your App
INSERT
πŸ” d-stack (TEE) encrypt β†’ Postgres
WAL via SHOYU
πŸ”’ Replica
πŸ”’ Replica
πŸ”’ Replica
Replicas store ciphertext. Only d-stack decrypts.
🧈
TOFU
Trustless on first use

Hardened by silicon.
Softened for you.

01

Deploy to d-stack

Push your TOFU configuration. TEE attestation verifies the environment before secrets are provisioned.

02

Establish Trust

First connection triggers TOFU handshake. Cryptographic identity verified, then cached for future sessions.

03

Proxy & Replicate

Route SHOYU streams through encrypted proxies. Sync Postgres and application state across your infrastructure.

04

Scale Securely

Add nodes without re-keying. Trust propagates through your verified infrastructure automatically.

Every row. Every state. Every secret.

S3 + Vault + PgBouncerDIY Terraform Cloud + RDSTFC+RDS Spacelift + Secrets MgrSpacelift TOFU
Encryption Granularity Disk/TLS Disk/TLS Disk/TLS Row-level
Replicas See Plaintext Yes Yes Yes No
Encrypted in Use (TEE) βœ— βœ— βœ— βœ“
Node Revocation Re-key all IAM change IAM change Key rotation
Automatic Failover Manual Managed Managed 60-90s
Write Authorization App-level IAM IAM Row signatures
Hardware Attestation βœ— βœ— βœ— βœ“
Self-hosted βœ“ βœ— βœ— βœ“

Postgres is just the start. TOFU encrypts and replicates your Terraform state, application configs, and sealed secrets. Row-level encryption for your entire infrastructureβ€”replicas store ciphertext they can't decrypt. Revoke a node with key rotation, not re-encryption.

Under the Hood

Row Encryption
XChaCha20-Poly1305
Key Exchange
X25519 (proxy re-encryption)
Signatures
Ed25519 (optional row signing)
WAL Sync
Mutable soy + WAL replay
TEE Support
Intel TDX
Attestation
DCAP
Failover
Lease-based, 60-90s automatic
Deployment
d-stack / OCI Containers

Part of the Family

🧈

Welcome to the private era.

TOFU is currently in development for d-stack. Get in touch to discuss early access for your infrastructure.

Follow @secretnodes