Your Data Is Yours.
Forever.
Scientific data should stay portable and reviewable. TARE is being built around exportable records, evidence references, and open handoff paths instead of trapping operational history in one interface.
Standard JSON Export
Your inventory, experiments, and sample data are structured. Your export should be too. We provide a complete, nested JSON dump that preserves relationships.
No "Exit Fee"
Legacy systems charge you to leave. We don't. The "Export Data" button is available in your settings from Day 1, for free.
Portable Schema
Our data model is open. If you decide to migrate to a custom internal database, you can map our schema directly to PostgreSQL.
How it works
We stream your data directly from our edge-optimized database. Large datasets are handled efficiently, ensuring you get everything without timeouts.
- Authenticated API Route (`/api/export`)
- Streamed Response (Mock-Zero Latency)
- Cryptographically separate Tenant IDs
{
"metadata": {
"system": "TARE",
"exportedAt": "2024-03-21T10:00:00Z"
},
"organization": {
"name": "Acme Labs",
"id": "org_..."
},
"inventory": [
{
"name": "Acetone",
"cas": "67-64-1",
"quantity": 500,
"unit": "ml"
}
],
"experiments": [...]
}Reviewable Provenance
TARE links records, samples, materials, attachments, custody events, and exports into a reviewable history. Hashes and signed bundles help support integrity review, but formal provenance claims still depend on the scoped workflow and validation context.
Immutable Hash Chaining
Every action taken in the platform—from weighing a chemical to attaching an instrument read—is sealed with an unalterable SHA-256 payloadDigest. Modifying historical data invalidates the signature of every child event mathematically chained to it.
Multi-Parent Convergence Arrays
Real science isn't linear. High-throughput synthesis involves pooling aliquots from dozens of source tubes simultaneously. TARE natively leverages deep PostgreSQL Array matrices (parentHashes: text[ ]) to stitch complex genealogical lineages into a single, high-performance database row without relying on brittle relational joins.
