Built on the same principles
we help you implement.

All infrastructure is defined in Terraform and version-controlled. Infrastructure changes go through the same peer-review process as application code, providing a full audit trail.

Decern is multi-tenant by design. Every database query includes an org_id filter enforced at the repository layer — not the handler layer — so tenant isolation cannot be bypassed by application logic. No cross-tenant data access is possible through the API.

Field-level encryption for PII and wallet addresses at the application layer is on our roadmap. Currently these fields are protected by Neon's volume-level AES-256 encryption and tenant isolation via org_id scoping.

• Branch protections — master is always deployable with no direct pushes. All changes go through peer-reviewed PRs.
• Automated testing — Integration tests run against real databases, not mocks. Linting and type checking enforced in CI.
• Infrastructure as code — Terraform for all infrastructure. Every change is version-controlled, reviewed, and auditable.
• Squash merge only — One commit per PR for a clean, auditable history.

• Least privilege — Production access is currently limited to a single founder. As the team scales, we will enforce role-based access with SSO and documented access approval workflows.
• Secrets management — GCP Secret Manager for all sensitive configuration. No secrets in code or environment files.
• Scoped API keys — Keys can be restricted to specific permission sets to limit blast radius.
• SSO authentication — WorkOS AuthKit for dashboard access with enterprise SSO support.

As a founder-led company, incident response is currently handled directly by the founder with 24/7 alerting via GCP Cloud Monitoring and Sentry for application errors. Every alert routes to a single on-call individual — there's no ambiguity about ownership.

1. 1 Detection — GCP alerting and Sentry surface issues immediately
2. 2 Containment — Isolate affected systems, prevent further impact
3. 3 Resolution — Fix the root cause, not just the symptoms
4. 4 Communication — Notify affected customers with clear impact and remediation details
5. 5 Post-mortem — Document what happened and how we prevent recurrence

Service availability is continuously monitored via an independent platform with a public status page. As the team grows, we will formalize on-call rotations and escalation procedures.

Audit logs are stored in PostgreSQL for queryable access and dashboard views, and written to WORM (Write Once, Read Many) blob storage as the immutable source of truth. This is the same audit logging infrastructure we provide to our customers.

Neon provides continuous backup with point-in-time recovery, allowing restoration to any point within the last 30 days.

Infrastructure is fully defined in Terraform, so the entire stack can be reproduced from code in a new environment if needed.

• Go modules — Dependency integrity verified via Go module checksums.
• Node.js — Lock files pinned and committed. Automated dependency updates via Dependabot.
• Terraform providers — Version-pinned in configuration.
• Automated scanning — Dependabot monitors all repositories for known vulnerabilities and opens PRs for updates.

Formal SOC 2 Type 2 certification is on our roadmap. We're building with SOC 2 controls in mind from day one — branch protections, audit logging, access controls, and infrastructure-as-code are all foundations that make the eventual audit straightforward rather than a retrofit.