Security

    Reliability & Security

    At Voltade, reliability and security are foundational. Our products serve end-users globally, so our services must be fast, available, and secure—everywhere and at all times.

    Last updated: November 2, 2026

    Security Architecture & Perimeter

    We design for "least privilege" and minimal attack surface across identity, network, and application layers.

    • Identity & access: Production access through AWS IAM Identity Center SSO; application sessions hardened with Better Auth; enforced MFA for all privileged accounts; keys and secrets stored in cloud KMS/secret stores with rotation.
    • Network controls: Cloudflare WAF + firewall rules in front of all public endpoints; private networking for internal services; rate limiting and pagination on public APIs.
    • Tenant isolation: Per-tenant scoping, row-level security, and service-to-service identity; no cross-tenant data access paths.
    • Developer access: Principle of least privilege, regularly reviewed; unused tokens/SSH keys removed; audited admin paths; break-glass procedures tested.

    Volty Infrastructure

    Our stack is built for resilience and hosted in Singapore.

    • Cloud providers: Volty runs on AWS (Singapore, ap-southeast-1), fronted by Cloudflare for global Anycast, WAF, and caching.
    • Orchestration: Containers on Amazon ECS (Fargate) with autoscaling.
    • Databases: Amazon Aurora Postgres, with RDS Proxy for connection pooling.
    • Workflows: A Postgres-backed job queue (pg-boss) for background jobs and retries.
    • Observability: Logs, metrics and alarms in Amazon CloudWatch; error tracking and traces in Sentry.
    • Source & CI: GitHub hosts repositories, and GitHub Actions runs the pipelines; container images are scanned on push.

    Availability Monitoring

    We monitor production to detect issues quickly.

    • Amazon CloudWatch alarms on the production services.

    Alerting & Incident Response

    When signals breach SLOs, we escalate rapidly with clear ownership and communication.

    • 24/7 on-call rotations with multi-channel paging.
    • Runbooks for common scenarios (db failover, queue backlog, auth outage, cache issues).
    • Transparent user updates for material incidents and a public status page where applicable.
    • Post-incident reviews with documented RCA and preventive actions.

    Service Recovery

    We prefer safe rollbacks to last known-good over risky hot-patches in production.

    • Restart workloads and autoscaled deployments first.
    • Roll back to a healthy release for code-only changes; schema changes are fixed forward.
    • Escalate to extended maintenance only when necessary, with fixes tested in staging before release.
    • No untested changes in prod—avoid cascading failures.

    Data Protection

    We minimize data exposure and secure data in transit and at rest.

    • TLS everywhere; storage encryption; least-privilege data access.
    • PII logging is off by default; redaction/masking in logs and traces.
    • Per-tenant isolation (RLS and scoped tokens) to prevent cross-tenant access.
    • Cloudflare in front of all public surfaces (WAF, bot management, TLS termination).

    Logging & Observability

    We instrument everything that matters, without capturing unnecessary personal data.

    • Structured application logs and metrics to Amazon CloudWatch; errors and traces to Sentry.
    • Business-event logs (e.g., verification emails, integration setup) for fast diagnosis.
    • Background jobs record their outcomes and retries, and a job that runs out of retries pages Sentry.
    • Provider logs (AWS CloudWatch) plus Cloudflare logs feed anomaly alerts.

    Redundant Infrastructure

    We assume components—and sometimes providers—will fail, and design for graceful degradation.

    • Stateless services behind Cloudflare + cloud load balancers for horizontal scaling.

    Backups & Disaster Recovery

    We plan for the unexpected with clear objectives and practiced recovery.

    • RTO (target): ≤ 6 hours for complete downtime.
    • RTC (current): ~1–3 hours depending on incident scope.
    • RPO (target): ≤ 12 hours.
    • RPC (current): ~10 minutes–1 hour via Aurora point-in-time recovery.
    • Automated backups & PITR: AWS Aurora 14-day point-in-time recovery for Volty; restore drills performed regularly.
    • Backup storage: Encrypted backups written to AWS S3 in Singapore (single-region). There is no cross-region or cross-cloud replica.

    Testing & Rollbacks

    We ship safely with automated tests and a rollback path.

    • Every change runs lint, typecheck and tests in GitHub Actions before it deploys.
    • Unit and integration tests.
    • A regression is rolled back immediately for code-only changes, and fixed forward when a schema change shipped with it.

    Software Updates & Patch Management

    Volty is delivered as a multi-tenant hosted service. Customers do not install, host or patch any Volty software component, and therefore carry no patch-implementation obligation. Every security patch, dependency update and application release is designed, tested and deployed centrally by Voltade.

    Our commitments to you

    • Critical and important security patches are applied within 48 hours of a fix becoming available.
    • No update reaches production without passing the automated verification gate — production build, full type check, static analysis, dead-code and dependency checks, component tests, and the integration suite run against a real database with migrations applied. A failure blocks the deployment outright.
    • Compatibility testing is performed in a staging environment before any operating system, dependency or application update is promoted.
    • Updates are delivered without a version-pinning option: you always run the patched version, and receive it on your next page load.

    How we tell you

    • Release notes for each material release are published at voltade.com/product-updates.
    • Any change requiring action on your side — a browser minimum-version change, an integration credential re-authorization — is sent in advance to your named administrators and flagged on the release note.
    • Planned maintenance windows and live service health are published at status.voltade.com.
    • Security-relevant patches affecting customer data are communicated directly, in line with our incident and breach notification commitments.

    What we ask of you

    • Keep your web browser current. Volty supports the two most recent major versions of Chrome, Edge, Safari and Firefox.
    • Keep the devices used to access Volty patched and set to receive automatic operating-system updates.

    DDoS Protection & Caching

    We defend against volumetric and application-layer attacks without blocking legitimate users.

    • Cloudflare WAF, bot management, and global CDN shielding origin infrastructure.
    • Tiered caching and origin shields; surge queues and rate limits on dynamic endpoints.
    • Challenge flows (e.g., captcha) for suspicious traffic while keeping UX smooth for real users.

    Independently Verified Controls

    The following controls were verified against our live production account on August 19, 2026, by command-line query and console capture. The full evidence pack is available to enterprise customers under NDA.

    • Operational log retention: All seven production service log groups retain 12 months of logs, managed as infrastructure-as-code and confirmed against the live account.
    • Database encryption at rest: The production Aurora cluster and every automated snapshot are KMS-encrypted. Storage encryption was confirmed on the cluster and on the five most recent automated snapshots.
    • Object storage, application files: Versioning enabled. Default encryption is SSE-KMS with bucket keys. Customer-supplied-key uploads are blocked.
    • Object storage, inbound mail spool: Default encryption is SSE-KMS under a dedicated customer-managed key, with bucket keys enabled, and objects auto-expire after 30 days. Verified end to end with a live test message. Versioning is deliberately off: this is a delete-after-ingest spool, and retaining deleted mail versions would work against data minimization.
    • Audit trail: The management-event trail has logged continuously since 2023: multi-region, global service events included, log-file integrity validation on, and log files SSE-KMS encrypted under a dedicated customer-managed key.
    • Threat detection: AWS GuardDuty is enabled on the production account, with findings published every six hours.
    • Workforce authentication: Two-step verification is enforced for all users in the corporate domain, at the top-level organizational unit, with no exceptions and no opt-out. Administrative console sign-in additionally requires a passkey.

    Verified August 19, 2026 in ap-southeast-1 (Singapore).

    Trust & Transparency

    • Clear incident communications and status updates for material events.
    • Engineering runbooks and security practices documented for internal and customer reviews.
    • Customer data remains the customer's; we practise data minimization and purpose limitation.

    Contact Our Security Team

    For security questions or to report a potential vulnerability:

    Security Email: team@voltade.com

    General Inquiries: team@voltade.com

    Address: 75 Ayer Rajah Crescent #01-16, Singapore 139953

    We take security reports seriously and aim to acknowledge verified vulnerabilities within 24 hours.