Platform
The architecture behind one enterprise operating system.
Oxyra One Core, Oxyra Intelligence and the 71 Oxyra One domains are built as one governed platform — shared services and shared intelligence underneath independently activatable business capabilities, rather than 71 disconnected applications stitched together after the fact.
Product Family Model
Five layers, one platform.
Every Oxyra One product is built on the same foundation. Two additional flagship platforms sit alongside Oxyra One rather than inside its domain catalog.
- Oxyra One Core
- Shared identity, tenancy, security, administration, billing, workflow, integration, files, audit and platform services.
- 71 Oxyra One Products
- Independently activatable business and capability products, licensed and enabled per tenant as needed.
- Oxyra Intelligence
- Shared intelligence, AI, prediction, recommendation, retrieval and automation layer used across every domain.
- Oxyra Forge
- A separate flagship software engineering and delivery platform — not part of Oxyra One's domain catalog.
- Oxyra QuantPilot
- A separate flagship quantitative intelligence and research platform — not part of Oxyra One's domain catalog.
Shared Platform Services
Every domain is built on the same shared services.
Oxyra One Core provides one set of platform services that every one of the 71 domains relies on, instead of each domain reimplementing its own identity, storage, workflow or reporting layer.
- Identity and authentication
- Tenant and organization hierarchy
- RBAC and policy authorization
- Subscription and entitlement management
- Billing and usage metering
- Audit and compliance logging
- Notifications
- Document and file storage
- Workflow engine
- Search
- Integration Hub
- AI Gateway
- Knowledge retrieval
- Reporting and analytics infrastructure
- Observability
- Background jobs
- Configuration management
- Feature flags
- Localization and currency framework
- Data import/export
System Graph
A dependency map for every change.
Oxyra One maintains relationships across every layer of the platform — from a product down to the AI agents that act within it. This graph is the dependency map that administration and the change engine use to understand the impact of any change before it happens.
- Product
- Entity
- Field
- Relationship
- API
- Screen
- Permission
- Workflow
- Automation
- Report
- Integration
- AI Agent
Oxyra Enterprise Graph
A long-term intelligence foundation across every domain.
Beyond the technical System Graph, Oxyra One maintains the Oxyra Enterprise Graph — the connections between business objects and relationships across domains. A few examples of the kinds of relationships it connects:
- People ↔ Teams ↔ Skills ↔ Projects
- Customers ↔ Contracts ↔ Orders ↔ Invoices ↔ Support
- Suppliers ↔ Procurement ↔ Contracts ↔ Quality ↔ Payments
- Assets ↔ Maintenance ↔ Service ↔ Costs ↔ Utilization
The Oxyra Enterprise Graph is tenant-aware, permission-aware, auditable and versioned. AI only traverses the relationships that the requesting user or service is already authorized to access — the graph never expands what a user or an AI agent is allowed to see.
Enterprise Memory
Governed organizational knowledge, not an unrestricted AI memory store.
Enterprise Memory holds governed organizational knowledge — policies, procedures, contracts, historical decisions, and customer or supplier history — so it can be retrieved consistently across the platform. It is explicitly not an unrestricted AI memory store: every piece of knowledge in it carries governance metadata.
- Source provenance
- Access controls
- Retention policies
- Versioning
- Tenant isolation
- Sensitivity classification
- Retrieval authorization
- Auditability
- Confidence and freshness metadata
Self-Evolving Software
Software that can change itself — under governance, not on its own.
Oxyra One is designed so that some changes to the platform can be proposed, evaluated and applied through a governed lifecycle, rather than always requiring a full manual engineering cycle. Every change — no matter how it originates — passes through the same stages:
- Intent
- Permission Check
- Impact Analysis
- Change Plan
- Risk Classification
- Implementation
- Testing
- Preview
- Policy Gate
- Deployment
- Verification
- Audit
Low-risk configuration changes may be automatable after validation.
Medium-risk business changes require tests and configurable approval.
High-risk security, tenant-isolation, infrastructure or breaking changes always require explicit human or engineering approval.
Technology
Built as one platform, not a patchwork.
Oxyra One is built on a unified enterprise backend and a modern web frontend, running on Microsoft Azure cloud infrastructure. The architecture follows domain-driven design with strict domain boundaries between the 71 products — giving each domain room to evolve independently without becoming either an unmanaged monolith or a sprawl of 71 separate microservices.
Frontend
A modern web frontend built with Next.js, React and TypeScript.
Backend
A unified enterprise backend built on ASP.NET Core / .NET in C#.
Architecture
Domain-driven design with strict domain boundaries — not an unmanaged monolith, and not 71 separate microservices.
See the platform in your own environment.
Talk to us about which capabilities are relevant to your organization.