TELOS · FAQ
Questions, answered plainly.
What's the difference between Foundry and Nexus?
Foundry is where you model: it resolves source data into typed, RID-addressable objects with links, lineage, and markings. Nexus is where you operate: it promotes actions across environments, watches health, and rolls back. They share the same objects, so there's no translation layer between them.
Do I have to use both products?
They're designed to be used together — that's the whole point of one system — but you can start with Foundry's model or Nexus's operations and grow into the other.
Can Telos run in an air-gapped environment?
Yes. Nexus can deploy into isolated or air-gapped networks where data never leaves your boundary. The control plane comes to the deployment rather than pulling data out.
How does governance work?
Markings (including PII and access markings) attach to the object and enforce at query time across both products. Every read, write, and promotion is recorded to an immutable, queryable audit log with configurable retention.
Is Telos generally available?
Not yet — we're rolling out to a small set of operators first and reviewing every access request by hand. Request access and tell us what you run.
What does it cost?
Pricing depends on scope and deployment model. We'll discuss it directly during access review rather than publish a number that wouldn't fit your situation.
TELOS · REQUEST ACCESS
Still have a question?
Ask it on the access form — a person reads every one.
Request access