Your ontology determines what's possible in Foundry. Get it wrong and you're rewriting pipelines and applications for months. We design ontologies that work from day one and scale as you grow.
Your ontology is the foundation everything else builds on. Object types, relationships, properties—these decisions affect every pipeline, every Workshop app, every query your users run. Get them wrong and you'll be rewriting things for months.
Most teams start by mapping their database tables directly to object types. That works until it doesn't. Then they realize their relationships are backwards, their property types don't match actual use cases, and their security model doesn't support what they need to build.
Object types that match how your organization works. Properties with the right data types, validation rules, and structure to support actual use cases.
Link types that capture how objects connect to each other—with the right cardinality, directionality, and business meaning. This determines what questions users can answer and what workflows are possible.
Row-level security policies, restricted views, organization markings for multi-tenant setups, and property-level access controls where needed. Security designed in from the start, not bolted on later.
Action definitions with validation rules, permission checks, and parameters configured for the workflows your users need to perform in Workshop applications.
If you're building for multiple customers or business units, your ontology needs to support organization isolation while allowing controlled data sharing. This requires careful space and security design from the beginning.
We've built B2B and B2C architectures on Foundry before. We know how to structure organizations, configure restricted views properly, and handle the edge cases that trip people up.
You get a fully documented ontology with object types, properties, links, and actions implemented in your Foundry instance. We also provide documentation explaining the design decisions and how to extend it as your needs grow.
If your team is maintaining this long-term, we walk through the design with them so they understand why things are structured the way they are.
Tell us about your data and what you're trying to build. We'll propose an ontology design approach.
Get in touch