Architecture
The system runs as a serverless web application backed by a managed Postgres database and private object storage. Each deployment is a dedicated instance: one contractor, one database, one storage bucket, one domain. Your records are not co-mingled with another company's tenant data because there are no other tenants.
Application Hosting
Vercel (serverless functions + CDN). All traffic is served over HTTPS with TLS 1.2+.
Database
Supabase managed Postgres (AWS). Encrypted at rest and in transit. Media and documents live in a private, non-public storage bucket.
Email Delivery
Resend transactional email. Quote links and notifications are sent over TLS.
Access & Authentication
- Contractor surfaces (admin, financials, exports) require a contractor credential. Every administrative API call is authenticated; unauthenticated requests receive
401. - Field workers authenticate with a per-worker credential bound to their vendor record. Workers can read and write only their own shifts — they cannot view another worker's timecards, set their own pay rate, or reach administrative actions.
- Clients access their quote and change-order pages through single-use public tokens embedded in their quote link. Client-facing responses are sanitized: vendor rates, internal notes, and request metadata never leave the server.
- Signatures & approvals record an audit trail: signer name and email, consent text, timestamp, IP address, user agent, document version, and a SHA-256 fingerprint of the exact document approved. Signature images are stored as files in private storage — never as base64 in the database.
- Rate limiting is enforced on public and credential-guessing endpoints (lead intake, PIN checks, worker auth, public ticket submission) as a fixed-window per-IP brake.
Data Protection
- In transit: all traffic (browsers, field phones, API calls, webhooks) uses TLS.
- At rest: database and object storage encryption is provided by the managed platform (Supabase/AWS).
- Media: receipts, signature images, W-9s, COIs, and lien waivers are stored as objects in a private bucket and served only through an authenticated media route.
- Secrets: API keys, database credentials, and signing configuration live in server-side environment variables, never in client code, exports, or logs.
- Financial records are voided, not deleted: voided expenses and payments keep an audit trail (reason, timestamp) and are excluded from accounting exports.
Backups & Availability
- Nightly automated backup: a scheduled job writes a full snapshot of every data table plus a media manifest to private object storage, timestamped, with no manual step.
- Managed database recovery: Supabase continuous backups / point-in-time recovery are enabled on paid tiers. Recommended for any production instance carrying live financials.
- Field resilience: crew phones keep working with zero signal. Punches and job notes queue on the device in a durable outbox and replay automatically when connectivity returns, with per-record status tracking.
Your Data, Portable
Full-Exit Export
One click in the admin panel exports every table (leads, expenses, payments, receipts, vendors, quotes, change orders, timecards, households, contracts, lien waivers, purchase orders, floor plans) as JSON plus per-table CSVs suitable for your accountant, including a manifest of every stored media file. Your data is yours; leaving is a download, not a negotiation.
Error Monitoring
Optional per-instance error reporting (Sentry) can be enabled with one environment variable. Telemetry payloads are scrubbed: PINs, tokens, and credential-looking fields are redacted before leaving the app, and URLs carrying credentials are masked in breadcrumbs.
Legal & Document Accuracy
Lien waivers and other generated documents are templates, not legal advice. The default lien waiver template is written to Wisconsin statute (Wis. Stat. ch. 779) and is pending independent legal review. Lien law varies by state, so have your construction attorney review and adapt every template for the states you work in before relying on it.
Responsible Disclosure
Found a vulnerability? Report it directly and we will respond promptly:
- Email: support@buildoperations.app
Please include reproduction steps and avoid accessing or modifying data that isn't yours. We investigate every report, fix on a priority basis, and notify affected parties when required.
Honest Limitations
- Rate limiting is per serverless instance. A strong brake on abuse, not a globally distributed quota. Managed WAF/CDN rules are recommended for high-traffic instances.
- Until magic-link authentication ships, the credential model is PIN-based with worker scoping. Adequate for a single-contractor deployment, and deliberately scheduled for upgrade before multi-contractor rollout.
- E-signature records capture a tamper-evident audit trail designed for ESIGN/UETA-style defensibility, but are not a substitute for legal counsel on enforceability in your jurisdiction.
