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.

Health gate ready

Public status is operational. Finish human production proof before launch traffic.

Live health probes, last checked 2026-07-30 10:43:30 UTC · refreshes every 60 seconds

View status Security overview Try demo

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

Implemented

aa0ec53

The build this snapshot was generated from. Certification is scoped to a single frozen commit.

Production evidence

Pending

18 of 20 recorded

Secret-free go-live evidence checks with live or customer-test proof attached to each item.

Authenticated E2E

Pending

Not yet run

The signed-in Playwright suites skip in CI until the Clerk E2E user secrets are configured. No authenticated pass has run yet.

Production migrations

Production-verified

Applied through 107 (local latest 107)

Schema migrations confirmed applied to the production database.

Legal counsel review

Pending

Governing-law and auto-charge/refund terms are awaiting counsel sign-off before certification.

Code gates

Verified

Status, env, copy, webhook, and Connect tests exist.

Production health

Operational

Public health must be operational before launch traffic.

Integration evidence

Pending

Provider checks must be recorded before availability upgrades.

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

Rate limiting

Operational

Configuration

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

Production Vercel env vars pass the secret-safe production env checker
Stripe live Pro trial start and cancellation verified
Resend SPF, DKIM, DMARC, and inbox placement verified
Sentry receives synthetic frontend and backend errors
Disposable-user journey completed from signup through cancellation
Secret-free go-live evidence artifact is filled and passed

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

Email forwarding, CSV/ILPA, API keys, webhooks, developer console, and sponsor CSV/export intake are implemented.

Beta code paths

Gated

Outlook, Gmail, Plaid, Google Drive, Dropbox, OneDrive, and Zapier/Make require provider configuration or feature flags.

Direct sponsor sync

Request access

InvestNext, Carta, CrowdStreet, RealtyMogul, AppFolio, SyndicationPro, and SponsorCloud 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 still required

Once the domain has an MX record, verify a real inbound sponsor email end to end (attachment parsing plus recovery)
Connect Outlook with a real mailbox and verify sync, import, and disconnect
Complete Plaid sandbox and webhook matching checks before broad beta
Verify Drive, Dropbox, and OneDrive selected-file imports with real accounts
Run at least one private Zapier or Make recipe end to end
Record sponsor portal evidence before any direct adapter is enabled