System status
The API works. Production hardening is the launch gate — see what's implemented and what's still pending below.
01
Live API health
Status: checking…
Checked against the same /api/health endpoint the header status dot polls, refreshed every 60 seconds in your browser. This reflects whether the API is reachable right now — it is not a historical uptime record.
02
Readiness by use case
Operational gaps below do not all carry the same weight — this breaks readiness down by what you’re actually trying to do with LedgerBase.
- Public demo: Ready. The keyless, rate-limited demo on the homepage and the live API reference both work against the real API today.
- Developer evaluation: Ready. Self-serve API-key issuance, the read API, lineage, and data-quality endpoints are implemented and usable for integration testing and prototyping.
- Paid production usage: Not applicable yet. LedgerBase is free during early access — there is no pricing plan, billing, or paid tier to evaluate readiness for.
- Not yet production-ready:Production TLS, managed secrets, backups, rollback, external logging, and isolation of internal ingest endpoints — see “Before public launch” below. Do not run a business-critical workload against LedgerBase until these are addressed.
03
Implemented
Read API, scheduled SEC ingestion, lineage, data quality, API-key access, rate limiting, and operational endpoints.
04
Before public launch
Production TLS, managed secrets, backups, rollback, external logging, and isolation of internal ingest endpoints.
05