Services
EEP API (Railway)
Project, engine, and reports endpoints
NEC 2023 calculation engine
Article 220 / 430 / 240 / 517
CEC 2024 calculation engine
Rules 8 / 28 / 14 / 24 / Section 24
Authentication (Supabase Auth)
Login, session, JWT issuance
Database (PostgreSQL on Supabase)
Projects, results, audit log
File storage
Reports, SLD exports, evidence uploads
CDN (Cloudflare Pages)
Marketing and login surfaces
Webhooks & billing
Lemon Squeezy / Stripe integrations
How we report incidents
- Operational — no known issue, normal latencies.
- Degraded — some users see slower responses or partial features; engine output is unaffected.
- Outage — service unavailable; we post a banner inside the app and on this page.
If you see something off, email support with the project ID and approximate UTC timestamp — we can match it to logs in under five minutes.
Scheduled maintenance
Routine maintenance runs Sundays 06:00–06:30 UTC. We aim for zero downtime; if a deployment requires brief unavailability, we post a banner 24 h in advance.
Engine version policy
When we deploy a new version of the NEC or CEC engine, every cached engine_results row for the affected standard is marked is_stale = true automatically — your next open of the project recomputes against the new engine and writes a fresh audit log. You'll see a banner on the project page.