Solutions
One catalogue behind every vertical
The hard part of onboarding data is not the model — it is mapping every source’s layout to your schema without shipping raw records out. Each vertical below is the same six-layer cascade pointed at a purpose-built template pack.
- templates on GET /v1/templates
- 33
- packs the engine serves
- 7
- rated medium or high
- 13
- cascade layers, 3 of them free
- 5
- Headers + ≤3 rows, 80 chars each
- Three layers need no model
- HMAC self-contained API keys
- RLS on the dashboard plane
- Uploads in KV, 24h default TTL
- PHI in-region under a BAA
By vertical
Start from your data.
Pick the vertical whose files you already receive. Each page prints its pack’s real template ids, field objects, risk levels and validators — not a description of them.
Healthcare
Hospitals, labs and payers receive patient, lab and claims files in every possible shape. The healthcare pack maps them to FHIR R4 with LOINC, ICD-10, ATC, CPT and NPI validators — and in schema-only mode no patient record leaves your system to do it.
Pack · 10 templates · 4 medium + 0 high gate on review · 7 FHIR R4 resources
See the healthcare solutionFinance & payments
Banks, PSPs, ERPs and spreadsheets each export a different layout, and a transposed IBAN digit is expensive to find later. The finance pack maps four templates with a real mod-97 IBAN check, and three of the four gate on human review before commit.
Pack · 4 templates · 1 medium + 3 high gate on review
See the finance & payments solutionHR & people
HRIS, ATS and payroll vendors exchange some of the most sensitive PII a company holds, each in its own export format. In schema-only mode the cascade maps those files from headers alone — no employee record, no salary, no national ID is transmitted.
Pack · 4 templates · 1 medium + 2 high gate on review
See the hr & people solutionBusiness packs
Every SaaS has to ingest user lists, CRM contacts, product catalogs and orders, and no two customer exports look alike. Thirteen low-risk templates across three packs cover the common business objects — and most columns land on the free deterministic layers.
Pack · 13 templates · all low-risk, commits straight through
See the business packs solutionThe common thread
Different data, the same posture.
Whatever you map, four things hold. They are properties of the engine, not options on a plan — a healthcare workspace and an e-commerce workspace get the same guarantees.
Schema-only is the default posture
Headers and up to three sample rows, each clamped to 80 characters. That is the whole of what leaves your system to produce a mapping — a data-minimization mode, not a trial tier.
HowclampForSchemaOnly() in lib/parser.ts is the single chokepoint (≤3 rows, ≤80 chars per cell), applied at the HTTP edge in every /v1 route that accepts sample rows — so schema-only and full-data cannot drift apart.
The model is the last resort, not the first
Six layers, cheapest first. Statistics, heuristic and fuzzy are pure compute; a column that resolves on one of them never reaches a metered model at all, and a matcher we host ourselves takes most of what they leave. That ordering is the biggest cost lever in the system.
HowAuto-accept at {minN:100, minRatio:0.95} and {minN:20, minRatio:1.00} on statistics; fuzzy auto-accepts at 0.80 on token-set + Levenshtein. Contests are settled by layer rank then confidence — never by column order.
Risk is a property of the template
A template rated medium or high always comes back flagged for review — on every call, for every workspace, with nothing to configure and nothing to remember.
HowPATCH /v1/uploads/:id/mappings derives requires_hitl and hitl_status from the template’s risk field — 8 medium and 5 high across the catalogue today. We set the flag; your workflow owns the queue.
PHI routing is opt-in, in-region and gated
Full-data runs send the layer-5 call to phi-cloud with X-PHI and a region pin, so a PHI-eligible in-region model handles it under the BAA. Standard is what an unconfigured workspace gets.
HowLocked until the workspace accepts the BAA in Settings → Security & Data; an explicit PHI ask without one returns 403 agreement_required with a settings_url. PHI adds 20% to the whole map charge.
How to choose
Find the row that describes your inbox.
You do not have to know our pack names to pick a page. Start from the file you already receive; the vertical follows from it, and the last row is the answer when none of them fits.
| The files you receive | Where it goes | What it adds | The consequence |
|---|---|---|---|
| Patient, lab, claims or formulary files | Healthcare | FHIR R4 emit | LOINC / ICD-10 / ATC / CPT / NPI validated at map time |
| Ledgers, payouts, bank accounts, KYC | Finance & payments | mod-97 IBAN | no PAN field exists — masked card data by construction |
| Employee, payroll, leave or candidate exports | HR & people | PII minimisation | most files map without a complete record leaving |
| User lists, CRM dumps, catalogues, orders | Business packs | layout reuse | 13 low-risk templates; commits are not gated |
| A schema of your own, no template involved | The engine | same cascade | packs are a catalogue, not a gate — bring your own target schema |
The catalogue
Every pack, printed.
The full template catalogue behind these pages, with the risk mix that decides which mappings gate before commit.
| Pack | Templates | Risk mix | Solution page |
|---|---|---|---|
coreCore | 3 | 3 low | Business packs |
healthcareHealthcare | 10 | 6 low4 medium | Healthcare |
crmCRM | 5 | 5 low | Business packs |
ecommerceE-commerce | 5 | 5 low | Business packs |
financeFinance & Payments | 4 | 1 medium3 high | Finance & payments |
hrHR & People | 4 | 1 low1 medium2 high | HR & people |
evidenceClinical evidence & market access | 2 | 2 medium | Template packs → |
GET /v1/templates and GET /v1/packs are public and static, and return exactly this: 33 templates across 7 packs, 13 of them rated medium or high. A medium or high template makes PATCH /mappings return requires_hitl: true.Your vertical isn’t listed? The cascade still maps it.
Any CSV, Excel, JSON or SQL maps to a schema of your own on the same engine — packs are a catalogue, not a gate. Top up a $10 prepaid wallet and point it at your file.