Own your data. And the science behind it.
Ownership means understanding your data, controlling where it goes and retaining the history that makes it useful—even outside our applications.
The values. The meaning.
The history. Yours to use.
Our product direction gives customers usable copies of their scientific assets, permitted interpretations, labels and derivation records. Essential reading and export must remain available independently of a paid application UI.
Explore lineage and AI ↗Choose the environment.
Control the destination.
We are designing for customer-controlled storage, identity and compute, in a customer cloud or on premises. Managed hosting is an explicit option. Using ArrayBridge does not have to mean placing data in our SaaS account.
Supported source and destination choices start with portable bundles, then customer object storage and qualified application connections. Each transfer must check source access, destination permission, scope and conversion loss.
General source/destination configuration and customer bucket UI remain roadmap work. Extensible destinations do not imply every destination is already supported.
Keep the context that makes data valuable.
Identity, exact revisions, units, missing values, axes and coordinate claims travel with the values. Preserve original evidence where permitted. Unknowns stay visible.
Scientific lineage adds the recipe: inputs, calculations, parameters, software versions and review decisions. Your data should remain understandable after the application that created it is removed.
Prove that you can leave.
The exit test is concrete: export permitted originals, payloads, metadata, schemas and lineage; open them on a clean machine with an independent reader; verify hashes and meaning; reproduce a recorded calculation.
The requirement extends to permitted interpretation geometry, labels, dataset manifests and model outputs. Revoking future API access cannot recall already exported copies or undo model training.
Try a small independent-reading exercise →Pay for useful tools.
Keep usable access.
Our intended open foundation includes scientific contracts, schema extensions, reader/writer SDKs, export tools and compatibility fixtures, with reference connectors where host terms allow.
Commercial value comes from useful scientific applications, validated workflows, certified connector maintenance, analysis, hosting and support. Baseline security, essential lineage and usable exit are product requirements. Exact licenses and pricing remain undecided.