Potentially certifiable later
Exact contracted flat, unit, first/additional, and matrix mismatches, plus uniquely identified within-invoice duplicates, have the narrowest eligible proof shapes.
Live
Planned
Fictional sample
Prelaunch status
A public record of what exists—and what does not.
Auditario has a local, deterministic audit engine and a public waitlist. It does not yet have public document intake, an authenticated product, Shopify access, billing, or automated dispute sending.
Availability
The exact product boundary
“Built” does not mean “available to merchants.” Local engineering, public website behavior, and future application capability are kept separate below.
Live
Public information and waitlist
This site explains the methodology and accepts contact-only waitlist requests through a small Cloudflare Pages handler.
No account is created. No contract, invoice, payment, or Shopify data is accepted.
Built locally
Deterministic audit engine
Local Python tooling can parse CSV, XLSX, and native-text PDF fixtures, normalize supported layout families, execute versioned checks, seal outcomes, and generate reports.
This is operator software in a local workspace, not a hosted merchant service.
Fictional
Product previews
Dashboard, issue, and invoice previews show a possible future interaction model using invented organizations, invoices, dates, and amounts.
They are design references, not live accounts, customer outcomes, or provider allegations.
Planned
Authenticated merchant application
Magic-link sign-in, organizations, roles, dashboards, invoice and issue routes, approvals, recovery tracking, and the operator console remain future Phase 1A work.
There is no public login, tenant database, Railway application, or merchant API today.
Planned
Secure intake and connected evidence
Tenant-scoped R2 uploads, hostile-file validation, Postmark, Shopify OAuth and webhooks, and live model refutation are gated future capabilities.
Do not email or submit documents through the waitlist.
Planned
Billing and dispute automation
Flat subscriptions, guarantee credits, merchant-approved dispute dispatch, 24-hour notice, cancellation, and AutoPilot are not active.
Joining the waitlist is not a purchase, price reservation, or authorization to act.
Engineering evidence
Capability without overclaiming coverage
The repository can recognize several documented shapes. None is certified to publish a positive claim, and extraction-harness success is not provider adjudication.
0
claim-ready certification cells
3
provider layout families normalized locally
4
documented file-layout variants in the public corpus
$0
amount the present system may request in production
Review-only now
Effective dates, tiers, minimums, missing credits, storage continuity, and tax-on-gross-of-credits remain capped below claim-ready.
Observation-only now
Undefined charges, rate drift, insurance overlap, document integrity, and charge-code mapping can inform a review but cannot state money owed.
Layout support is not claim certification. A parser can read a shape accurately while a finding still lacks source integrity, governing terms, an established window, reconciliation, refutation, or evidence that excludes an innocent explanation.
Approved architecture
Cloudflare at the edge. Railway behind the application.
The target split is approved, but most of it is not deployed or implemented.
Cloudflare
The current public surface is static marketing plus one contact-only waitlist handler backed by KV, with server-validated Turnstile, same-origin enforcement, and a short-lived abuse counter. Future phases add zone-level WAF policy, tenant-prefixed R2, and later the event control plane.
Railway
The planned authenticated product uses separate React BFF, private FastAPI, Python worker, and PostgreSQL services. No Railway service or hosted production database exists today.
What changes this status
Evidence earns the next label.
A feature moves from planned to live only after its phase is explicitly authorized and its security, isolation, accuracy, and release gates pass.
- 01Authorize the phaseNo later-phase service begins merely because its design exists.
- 02Prove the boundaryTenant isolation, upload controls, sealed artifacts, and fail-closed model behavior must be exercised.
- 03Certify each cellReal held-out evidence and provider adjudication are required before positive claim publication.
- 04Report the gateAuditario publishes what passed, what remains unsupported, and the date of the assessment.