Custom Metamodel & Shapes
Every enterprise has its own terminology: internal cost center codes, regulatory classifications, SLAs, or custom technology types. Kyb provides a dedicated Metamodel Studio at /ontology where organization administrators can define custom classes, attributes, relationships, and SHACL shapes.
Tenant-Isolated Named Graphs
Your custom metamodel definitions are strictly tenant-isolated. They are stored in your organization's dedicated named graph in Oxigraph (e.g. urn:kyb:org-ontology:{orgId}) using the custom namespace (https://kyb.fyi/ontology/custom/). Your custom types are immediately available to all members of your organization and remain completely private.
1. Custom Classes
Create custom entity types that specialize or extend core ArchiMate layers:
- Parent Class Inheritance: Inherit from core ArchiMate classes (e.g., creating a SaaS Product subclassing Application Component).
- Layer Classification: Assign the element to an architectural layer (Motivation, Strategy, Business, Application, Technology) for automated swimlane layout.
- Custom Icons & Labels: Choose visual symbols and display labels for the canvas and element palette.
2. Custom Properties & Datatypes
Attach typed metadata fields to any entity or relationship. Kyb supports:
Freeform descriptions, identifiers, notes, or external system keys.
Numerical quantities, with optional currency formatting (USD, EUR, GBP, JPY).
True/false toggles (e.g., isInternetFacing, hasBackup).
Direct links to Jira epics, Confluence documentation, or Runbooks.
Controlled enum dropdowns (e.g., Tier 1 / Tier 2 / Tier 3, or Production / Staging / Dev). Maintains semantic consistency across all teams.
3. SHACL Constraint Shapes
Every property can be paired with automated SHACL constraint shapes:
- Required Fields (
sh:minCount 1): Mark properties as mandatory for specific entity classes. - Allowed Values (
sh:in): Enforce that only approved enum values are accepted. - Datatype Bounds: Validate minimum/maximum values on integers and decimal currencies.
Guided Concept Migration
When an administrator removes or renames an allowed option from a controlled vocabulary, existing entities might become invalid. Kyb prevents silent corruption through automatedImpact Checking:
Before the change is committed, the Concept Migration Modal displays every entity currently using the deprecated option, prompting the administrator to map the legacy values to a new replacement option or clear the property safely.
Next: Project Backups & Snapshots
Learn how to safeguard your graph with point-in-time backups and portable bundles in Backups & Snapshots.