Denton BBQ LLC · Business Continuity
Our Backup & Disaster Recovery Strategy
A website is more than its hosting account. We build recovery into our operations so that a provider outage, configuration mistake or unexpected incident does not leave a business dependent on only one copy of its critical systems.
Independent off-site copies
For participating projects, we export supported source-code repositories and production PostgreSQL databases to a private Amazon S3 recovery bucket, separate from our application-hosting platform.
Encrypt before storage
Backup archives are encrypted with age before upload. Decryption requires a separate private recovery key; our public website and client portals do not expose that key.
Retention and access controls
We use S3 versioning and Object Lock Governance retention. Our current recovery configuration uses a 30-day retention window; Governance mode permits authorized administrators to override a lock, so it is not an absolute deletion guarantee.
Scheduled checks and escalation
The current AWS workflow performs a scheduled daily backup and sends an alert when a build fails. A separate alarm checks for extended periods without a successful run. Monitoring reduces risk; it cannot guarantee that every recovery will succeed.
Practice restoring, not just saving
We verify recoverability by performing isolated restoration tests. Source-code and database recovery have been tested on our Matulevich family-site project. Tests for other projects and external integrations remain separate work.
What is and is not included
Our independent backup system currently covers supported GitHub source-code repositories and designated Neon PostgreSQL production databases. A database backup captures data and database structures; a code backup captures code and Git history. Neither automatically recreates an entire production environment.
Third-party systems, such as Kintone records, QuickBooks, Clerk identity-provider configuration, Stripe transactions, uploaded media, email, DNS settings and external SaaS data, need their own recovery scope and may require a separate solution. We do not imply these services are included in the GitHub/Neon backup job.
Backup availability, restoration time, retention requirements, handling of regulated information, and any dedicated recovery service are governed by the project's signed agreement. No backup strategy eliminates downtime, and backups are not a substitute for provider-native redundancy or application security.
Protection versus contractual service
What a managed recovery agreement adds
An existing backup can be stored for a client without a separate fee. What the client does not receive without an agreed paid recovery service is a dedicated priority response, scheduled client-specific restore exercises, contractual RPO/RTO targets, bespoke retention, or a detailed recovery runbook. Those are separately scoped commitments, not controls that are disabled when a billing checkbox is off.
| Service feature | Complimentary protection | Paid managed recovery — proposed |
|---|---|---|
| Independent encrypted backup copies | For supported sources where configured | For sources specifically listed in the agreement |
| Backup job alerts | Internal monitoring and troubleshooting | Defined notification and escalation contacts, if agreed |
| Restoration assistance after an incident | Best-effort, quoted separately where required | Scoped restoration assistance under an executed service schedule |
| Recovery request priority | No dedicated recovery-priority commitment | Documented severity and response targets, when negotiated |
| Restore-test frequency and evidence | Internal tests at Denton BBQ's discretion | Customer-specific test schedule and evidence when contracted |
| Recovery point and recovery time objectives | No contractual RPO or RTO | Explicitly agreed objectives only; never assumed |
| Retention beyond standard configuration | No separately guaranteed extension | Optional, quoted extended retention if technically supported |
| Project recovery runbook and reporting | Not a dedicated client deliverable | Included only to the extent detailed in the signed addendum |
The paid column describes services that may be offered in a signed addendum. Checking a billing box does not activate these commitments or authorize additional charges. Neither tier turns unconfigured third-party services into backed-up sources.
Review draft General Service Level Agreement → · Draft Backup & Recovery Addendum →
How backup billing works
Denton BBQ may provide baseline disaster-recovery copies as part of its internal managed operations, including on a complimentary basis. A separately billed backup or managed recovery service is charged only when it is included in the customer's agreed terms. A project may be backed up without a separate backup fee.
For questions about your project's backup coverage, retention obligations, or a documented restoration plan, schedule a consultation or open a support request through your client portal.
This page describes operational practices, not an additional warranty, regulatory-compliance certification or recovery-time commitment. We regularly review and improve these controls.