v0.4 — Account Plans & Sources
Quantinal v0.4 simplifies how capacity and data work: one account plan covers all your spaces, and Sources replace the old per-tracker vault / space-filesystem model.
Review the Breaking changes section before upgrading integrations. Per-space capacity billing is gone, and tracker data access now uses explicit source selection (max 5).
Overview
- Account-level plans — Storage and throughput are purchased once on your account; spaces are free organizational containers that share the plan
- Sources model — Data lives in sources — named paths within a space that hold your uploaded files. Attach up to five sources per tracker
- No tracker vault — Per-tracker vaults and the "space filesystem" mental model are removed in favor of sources
Breaking changes
Account-level capacity (replaces per-space plans)
Storage and throughput are no longer purchased per space.
| Before (v0.3) | After (v0.4) |
|---|---|
| Each space had its own storage and throughput with a monthly fee | One account plan sets total storage and throughput for the whole account |
| Creating a space required choosing capacity | Spaces are free to create (an active account plan is still required) |
used_gb reflected a space's slice of a dedicated plan | used_gb is a usage counter; billing enforces the cap on account storage |
What to change: Manage capacity in the console under Account → Plan (not per space). Tracker run throughput is enforced account-wide, and storage for uploaded files and tracker results counts toward your account plan.
Sources replace vault / space filesystem
| Before (v0.3) | After (v0.4) |
|---|---|
| Per-tracker vault plus a shared "space filesystem" | Sources — named paths on a space that hold your uploaded files |
fs_scope_sources: null meant "all sources in the space" | Pass an explicit list of source paths (max 5) when use_space_filesystem is true |
What to change: Create sources and upload files in the console under Space Edit → Sources, or via the Sources API. On each tracker, set use_space_filesystem: true and fs_scope_sources to an array of up to five source paths (e.g. /financials/). Trackers that previously relied on fs_scope_sources: null ("all sources") should be updated to an explicit list — until re-saved, existing trackers may still run with the legacy interpretation.
API validation: fs_scope_sources longer than 5 entries returns 422 on tracker create/update.
Related documentation
- Space — Free project containers
- Tracker — Sources — Attaching data to trackers
- Pricing — Account plan rates
- API Reference — Endpoints — Updated Spaces and Sources sections