Public launch readiness
Service probes green. Production launch is not yet certified.
A green service probe means the app responds. It does not mean the production launch is certified. This page separates the two: live health below, and the certification state, which is not yet complete, in the panel that follows. No secret names, no internal error details, and no customer-count claims until they are real and permissioned.
Public status is operational. Finish human production proof before launch traffic.
Live health probes, last checked 2026-09-13 19:25:31 UTC · refreshes every 60 seconds
Production certification state
The production launch is not yet certified. Each fact below is tagged with what has actually been proven: implemented in code, tested in CI, or verified in production.
Levels:ImplementedCI-testedProduction-verifiedPending
Audited commit
Implemented0d25972
The build this snapshot was generated from. Certification is scoped to a single frozen commit.
Production evidence
Production-verified22 of 22 recorded
Secret-free go-live evidence checks with live or customer-test proof attached to each item.
Authenticated E2E
CI-tested469 passed, 0 failed (run 32611909680)
Signed-in Playwright suites passed against the staging project on 4ec1e27. CI-tested rather than production-verified: the lane deliberately never points at production.
Production migrations
PendingApplied through 191 (local latest 192)
Migration 192 is in the repo but not confirmed applied to production. Code merged ahead of the schema it depends on.
Legal counsel review
ImplementedSigned off
Outside counsel reviewed and approved the governing-law and auto-charge/refund terms. Recorded 2026-08-09 on the owner's attestation; counsel is not named here by their choice. This item is an attestation rather than a machine-verified artifact.
Production health
Operational
Public health must be operational before launch traffic.
Integration evidence
Verified
Provider validation evidence recorded for every source marketed as live
Current public health gate
These labels use public-safe messages only. Detailed diagnostics remain behind the admin status surface.
Application
Operational
Database
Operational
Payments
Operational
Operational
AI
Operational
Rate limiting
Operational
Schema
Operational
Configuration
Operational
Observability
Operational
Scheduled jobs
Operational
Verified before public launch traffic
- Public status output hides internal diagnostics
- Admin diagnostics require Clerk admin access
- Production-required env vars are documented in the canonical manifest
- Outbound webhook delivery uses at-most-one active claim per delivery row
- Pricing copy policy is guarded by tests
- Connect Hub and admin validation ledger are implemented
- Direct sponsor portal adapters stay gated until real validation evidence exists
- Go-live production evidence has a machine-checkable launch gate
- Local migration manifest has a machine-checkable Connect launch gate
Pending live verification
Read straight from the go-live evidence ledger, where 22 of 22 checks currently carry recorded proof. These are the ones that do not.
Integration readiness
SyndTrack Connect has the product surface for investor-owned data ingestion. Provider availability is still separated from implementation: anything that needs real OAuth, bank, cloud, or sponsor credentials stays beta or request-access until verified.
Live code paths
Built
CSV and ILPA, API keys, and Outbound webhooks are implemented and usable in production today.
Beta code paths
Gated
Email forwarding, Outlook, Gmail, Plaid cash matching, Google Drive, Dropbox, OneDrive, and Zapier and Make need provider configuration, credentials, or a feature flag before they do anything for a customer.
Direct sponsor sync
Request access
Sponsor portals accept CSV and export intake only, and are not marketed as live direct sync.
Trust rule: show the real state.
We will publish customer proof only when customers consent, keep AI outputs reviewable, and mark production and provider checks as pending until they are verified in live or customer-test mode.
Integration evidence by source
- Live code paths: Built. CSV and ILPA, API keys, and Outbound webhooks are implemented and usable in production today.
- Beta code paths: Gated. Email forwarding, Outlook, Gmail, Plaid cash matching, Google Drive, Dropbox, OneDrive, and Zapier and Make need provider configuration, credentials, or a feature flag before they do anything for a customer.
- Direct sponsor sync: Request access. Sponsor portals accept CSV and export intake only, and are not marketed as live direct sync.