Trust¶
Three questions come up in every serious conversation about running our software against your data: how is it secured, what happens to our data, and where are you on compliance? A fourth follows close behind: when something breaks, how do you find out? This section answers them directly.
It also tells you what is not finished. We would rather you learn that here than discover it during a security review — and a vendor who only publishes the flattering half of the answer has told you very little.
Start here¶
| Page | What it answers |
|---|---|
| Security posture | The principles every Endeavor Engineering system is designed and operated against |
| AI in our engineering | How we use AI in development, and what it is not allowed near |
| Data handling and isolation | Where your data lives, how it is separated from other customers', and what is shared |
| Operational monitoring and incident response | How we find out when something we run goes wrong, what happens next, and how incidents are reviewed |
| Compliance posture | What we are pursuing, what is in audit scope, and what we can provide today |
Where the products actually stand¶
Security claims are only meaningful alongside an honest statement of maturity, so:
- The Seeq connectors are in production use. They run inside your own Seeq environment, against your own historians. They are covered by defined licensing and support, and each carries its own compatibility and support pages under Connectors.
- ForgeVault is available through an Endeavor Engineering engagement — provisioned and operated for you. The self-service managed offering is planned, not shipped.
- The multi-tenant VirtualForge cloud is under active development. The security and isolation architecture described in this section is a set of settled design decisions, and it is what we are building. It is not a description of a platform already serving production tenants, and we do not present it as one.
Where a page in this section describes something designed rather than running, it says so on the page.
Asking us for more¶
Much of what a security review needs is not a web page: a completed questionnaire, an architecture walkthrough, a subprocessor list, or a conversation with the engineer who built the thing you are asking about. All of that is available on request.
Reach us through the Endeavor Engineering resources hub, or your usual Endeavor Engineering contact. Where our software reached you through a channel partner, that route works too.