Datasets
Typed, governed lists with stable business keys, validation rules and immutable published versions.
Examples · shipping rates · countries · cost centres
Explore reference datasetsCountry codes, cost centres, parameters, mappings between applications, organisational hierarchies and rates. Manage them in one place, with typed schemas, review before publication, versioning and an API that supports historical reporting.
Publicly available for pilot users and testers. Not yet recommended for production use.
The --pre option is required during the public beta. Upgrade compatibility with stable 0.1.0 is not guaranteed.
What counts as reference data
Why spreadsheets stop working
Spreadsheets are useful tools, but they are not a reliable system of record for shared reference data. Files such as country_ lack an enforced schema, validation and version history, making it difficult to reconstruct the data used for a previous reporting period.
Today
No owner · no version · no history
refrncr
Reviewed, versioned, auditable
Every consumer
One source, same answer everywhere
Three shapes of reference data
Some reference data is a list of values. Other data defines relationships between systems or reporting structures. Refrncr supports all three using the same review, versioning and publication process.
Typed, governed lists with stable business keys, validation rules and immutable published versions.
Examples · shipping rates · countries · cost centres
Explore reference datasetsCrosswalks that relate codes between systems and immediately expose missing or invalid mappings.
Example · SAP cost centre → Salesforce territory
Explore mapping datasetsHierarchies that aggregate or provide insight into a dataset, with parent–child relationships and effective dates.
Examples · organisation structure · regional classification
Explore hierarchy datasetsThe product
Reference data should not be edited directly in production. Work in a draft, review changes and publish a new version when it is ready.
effective_date, or select an immutable version.# currently effective published data $ curl -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/cost_centers/records" # look up the mapping for one source code $ curl -G -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/sap_to_salesforce/lookup" \ -d source=1001 { "data": { "values": { "target": "EMEA-SALES", … } }, "version": {…} } # fetch a complete hierarchy snapshot $ curl -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/management/hierarchy" { "data": { "nodes": […], "records": […] }, "version": {…} }
Point-in-time API
Reference data changes over time. Historical reports should use the data and structure that were effective during the reporting period—not whatever is current when the report is generated.
# 1 · no parameters → current published version $ curl -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/cost_centers/records" # 2 · January–February → version 15 (Sales) $ curl -G -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/cost_centers/records" \ -d effective_date=2026-02-28 # 3 · version 15, checked against that date $ curl -G -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/cost_centers/records" \ -d version=15 -d effective_date=2026-02-28 # 4 · March–June → version 16 (Operations) $ curl -G -H "Authorization: Bearer $REFRNCR_KEY" \ "$REF/api/v1/datasets/cost_centers/records" \ -d effective_date=2026-03-01
A cost centre moves from Sales to Operations on 1 March. A report for the first half of the year, generated on 15 July, attributes it to Sales for January and February and to Operations from March through June. Refrncr preserves both states, so the report remains historically accurate and reproducible.
What you stop maintaining
Maintain each dataset in one place, with a named owner, a defined schema and validation rules. Systems consume the published data instead of keeping separate copies.
Edit in a draft and publish an immutable version when it is ready. The version history shows exactly which data was available at any point in time.
Manage mappings between systems as governed data. Every consumer uses the same published mapping, while missing and invalid mappings remain visible.
Keep the author, review decision, effective date and field-level changes together. The audit trail is created during the change process, not reconstructed later.
Editions
Start with the self-hosted edition and move to a managed deployment when you no longer want to operate the platform yourself.
Self-hosted, single organisation per installation. Start on embedded SQLite with zero infrastructure; move to PostgreSQL when it becomes a real production system.
Coming soon
Coming soon
| Capability | Community | Cloud Coming soon | Enterprise Coming soon |
|---|---|---|---|
| Datasets, typed schema & records | ✓ | ||
| Mappings & crosswalks | ✓ | ||
| Hierarchies | ✓ | ||
| Draft → review → publish | ✓ | ||
| Effective dating & point-in-time API | ✓ | ||
| Teams, permissions & audit | ✓ | ||
| Multi-user, multi-team | ✓ | ||
| Embedded SQLite quick start | ✓ | ||
| PostgreSQL | bring your own | ||
| Multi-tenant platform | — | ||
| Provisioning, quotas & billing | — | ||
| SSO / SAML / OIDC, SCIM | — | ||
| EU data residency | your infrastructure | ||
| SLA & commercial support | — |
✓ included · optional = available by agreement · — not applicable to this edition · planned = not shipped yet
Pricing
Community is free, and stays free. Cloud and Enterprise are coming soon.
€0forever
Unlimited editors · your infrastructure
Coming soon
Coming soon
Non-goals
Refrncr is designed for governed reference data that changes deliberately and relatively infrequently — not transactional or operational data that changes throughout the day. These are deliberate product boundaries, not gaps waiting to be filled.
Running it
Embedded SQLite, no infrastructure. One install, one command, a working instance with your own data in it.
PostgreSQL for serious multi-user production use, in your own network, under your own backup and retention rules.
Effective permissions in business language — View, Edit, Approve, Publish — with team-derived and direct grants both inspectable.
Secrets are shown once at creation. Afterwards you see the identifier and metadata; key creation and revocation are audited events.
Deploy
Source-available under ELv2, self-hosted and free to run forever. Import one real list — your cost centres, not a sample file — and publish it through the API before you decide anything else.
We can operate the same platform for you, including hosting, backups and platform maintenance.