Engineering
For teams that want requirements, delivery, and dependencies to hold together without maintaining three tools for it.
View Engineering Use CaseThe modern way of specification engineering
From requirement documents to a connected product model.
OakCore brings requirements, tests, risks, and delivery into one shared context. Teams see early what a change will affect and keep a clear view even in complex projects. AI also understands relationships and full context.
Our approach
One model that everything else builds on
OakCore does not primarily split work by layers such as customer, system, or software. Instead, content is grouped by features, so what belongs together in engineering stays together in the tool.
The foundation
The project graph
Requirements, tests, risks, and delivery are connected. Every connection describes how two elements relate and can be used semantically. That keeps the full context in view, and relationships can be used efficiently for AI-based analysis.
See graph and context- More context for better AI support Through the graph, the AI understands not just individual items but also how requirements, tests, risks, and other artifacts connect. That context enables more precise answers and better support across the engineering process.
- Model validation You define which attributes, relationships, and status changes are allowed in your project. OakCore checks that in the background and flags whatever does not fit. That helps you avoid technical debt and maintain high model integrity.
What builds on it
The AI in OakCore works with your project rather than with general knowledge. It knows the requirements, how they relate, and where delivery stands, so it can support you as well as possible.
- An assistant that knows your project Questions about requirements, dependencies, or consequences are answered out of your own specification.
- Quality Scoring Requirements are rated on clarity, testability, and completeness. You see early where something needs sharpening, not first in assessment.
In comparison
What OakCore does differently
Compared to classic RM tools, spreadsheets, and point solutions.
OakCore Other tools
Relationships Requirements, tests, and risks are connected in the model References inside documents, maintained by hand
Assessing a change Everything affected is one click away Someone on the team has to know where it hurts
Spec and delivery Tickets, code, and CI hang off the requirement Two worlds that drift apart
Project status Live in integrated dashboards Collected manually or via a third-party tool
AI Knows your specification and design documents Does not know your project
Audit Evidence builds up while you work Assembled shortly before the date
Regulated development
Evidence should not be built at the end
Medical devices, automotive, rail: the ground rules are the same everywhere. Requirements have to be traceable, changes have to stay controlled, and evidence has to be available at any time. Spread across separate documents, that turns into manual work before every audit.
Traceability in the graph
Requirements, tests, and risks live in the graph and are connected. Tickets, architecture, and code are linked through integrations, without copying them.
Controlled changes and approvals
Changes are versioned, assessed with impact analysis, and approved through reviews. The audit trail builds itself, so the evidence is there before anyone asks for it.
Industries and relevant standards:
Automotive
Medical devices
Aerospace
Rail
Machinery
ISO 9001 and comparable QM standards
Use cases
Who works with OakCore
The same specification, three points of view. Every role gets the view it needs to make decisions.
Leadership
For leaders who want to know where a project stands, which risks are open, and what a change really costs.
View Leadership Use Case
Sales & Purchasing
For teams that negotiate requirements with customers and suppliers and have to keep them in sync with delivery.
View Business Use CaseIntegrations
OakCore connects your toolchain
Jira, GitHub, GitLab, Enterprise Architect, and your CI pipelines all connect. Tickets and code stay where your team already maintains them. OakCore holds the link to the specification.
See integrations
Security and privacy
Built for regulated environments
Data protection and the requirements for trustworthy AI are part of how we build OakCore, not something added later on.
GDPR The platform is designed to support privacy-compliant processes and to take GDPR requirements into account.
EU AI Act Our AI features are built with the requirements of the EU AI Act in mind.
ISO 27001 The architecture is built to structurally support security requirements such as ISO/IEC 27001.
Frequently Asked Questions
Who is OakCore for?
Teams building requirements-driven products who need to stay on top of complexity: product, systems engineering, quality, and development. Especially when Excel, Word, or tickets are no longer enough and traceability, reviews, or standards like ISO 26262 and IEC 62304 matter.
Does OakCore replace tools like DOORS, Polarion, or Codebeamer?
OakCore is built as a modern alternative. Requirements live in a connected graph instead of rigid lists. You keep traceability, versioning, and governance, but work faster and with more transparency. That lowers development and approval costs and improves team satisfaction through intuitive, modern tooling.
From the blog
Thoughts on specification, quality, and modern product development.
A survey of quality
A short tour of quality standards, why quality will never become a no-op, and why solid specification work remains a core skill even in the age of AI.
Read
Why Specs Supersede Tickets in Times of AI Agents
When code becomes a commodity, specification becomes the core competency – challenging Scrum, tickets, and conventional development processes at their foundation.
ReadGet to know OakCore in an online demo
In a 30–60 minute session, we walk through a concrete example of how OakCore streamlines engineering workflows and supports your team from day one. You speak directly with the founders.