Security

Hardened by default.
Not on request.

Security configuration is part of every deployment, not an add-on. Every server we touch leaves with a defined security posture, documented controls, and no defaults left open.

Security pillars
01
Isolation by design

No shared tenancy. Every client deployment is on dedicated compute. Your workloads do not run alongside other clients' workloads. Your data does not traverse shared storage.

02
Access control

SSH key authentication only. Root login disabled. Non-root service accounts with minimal permissions. Firewall rules scoped to actual service requirements — nothing else open.

03
Secrets management

No credentials in plaintext. Environment variable injection via systemd or Docker secrets. No API keys committed to repositories. Secret rotation documented and testable.

04
Auditability

Structured logging on all services. Auth events captured. Remote log forwarding available. You can answer the question "what happened" without us being on a call with you.

05
Update posture

Unattended security upgrades enabled by default. Kernel patching documented in runbook. No dependencies left at EOL versions on delivery.

06
Monitoring

Health checks and alerting configured before handoff. Uptime monitoring, disk and memory thresholds, and service restart policies in place. Failures surface, not silently accumulate.

Standards

SOC 2-aligned configurations

We do not offer SOC 2 certification. What we do offer is infrastructure configured to align with the control objectives that matter most for founders building toward enterprise clients: access control, availability, confidentiality, and change management.

When your enterprise client asks what controls are in place, you should be able to answer specifically. The deployment documentation we hand off is designed to support that conversation.

  • Logical access controls documented per service
  • No default credentials on any component at delivery
  • Encryption at rest where applicable (LUKS, encrypted volumes)
  • TLS enforced on all external-facing endpoints
  • Backup configuration documented and verified
  • Incident response procedure included in runbook
  • Dependency inventory at handoff (packages, versions, EOL dates)
Transparency

What we won't claim

We won't tell you your infrastructure is impenetrable. No infrastructure is. What we will tell you is the exact controls in place, the attack surface that remains, and what monitoring will surface if something changes.

We do not offer penetration testing, red team assessments, or security audits. We deploy infrastructure with a defined and documented security posture. For clients who need a formal security audit, we can recommend qualified vendors.

Questions about
your security
requirements?

The discovery call is where we map your risk surface. Bring your requirements and we'll tell you what's achievable, what isn't, and what it costs.

Schedule a scoping call →
All deployments include security documentation · No extra charge