Structure
TraceBoardStructure and trace engineering work: requirements, tasks, bugs, tests, links, risks, hazards and baselines.
REQ-042
linked to implementation work
linked to implementation work
TraceBoard Suite
Traceable engineering for modern engineering teams.
Connect requirements, work, verification and evidence in one connected engineering system.
The engineering model stays deterministic and inspectable. AI can assist with importing, analysis, querying, generation and narratives; your team reviews what becomes committed engineering data.
Built with the rigor regulated engineering requires. Designed without the bureaucracy it doesn't.
The engineering model
One connected engineering model.
Engineering need
→Requirement
→Work
→Verification
→Evidence
01 — The foundation
One connected engineering model.
Requirements, risks, tasks, tests and evidence remain connected. Instead of scattering engineering relationships across separate tools and documents, TraceBoard Suite keeps the links available as the work changes.
Relationships stay meaningful
The model represents recorded engineering items and explicit relationships. Deterministic calculations can show what those relationships contain; they cannot infer a relationship that was never entered.
“Built with the rigor regulated engineering requires. Designed without the bureaucracy it doesn't.”
02 — Engineering chain
Make the path from need to evidence visible.
The chain is a model of connected engineering relationships, not a mandatory workflow. Use the entities that make sense for your project.
Engineering Need
→Requirement
→Work
→Verification
→Evidence
Example: regulated engineering chain
Hazard
→Risk
→Requirement
→Task
→Test
→Evidence
Recorded relationships can feed documentation, standards-aware evidence and review preparation where required.
03 — Fit the process to the work
Works for your level of rigor.
Use the structure you need. No unnecessary process overhead. TraceBoard Suite supports regulated and safety-critical engineering without requiring every team to adopt a regulated workflow.
Everyday engineering
For SaaS products, embedded software, industrial software, AI-enabled products and teams outgrowing spreadsheets.
- Start with requirements and tasks.
- Keep traceability available as the project grows.
- Add tests, baselines and evidence when they become useful.
Regulated / safety-critical engineering
For medical software, automotive, defence and industrial or safety-critical engineering where additional rigor matters.
- Model hazards and risks where applicable.
- Connect requirements, work, verification and evidence.
- Use controlled baselines and evidence-linked verification.
Start simple. Add hazards, risks, baselines, tests and evidence as your needs grow. These capabilities are available to everyone; they are not hidden behind a special compliance mode.
04 — The suite
Three connected tools. One engineering model.
TraceBoard, TraceDocs and TraceTest are specialized services with shared project and item references, operating around the same recorded engineering data.
Document
TraceDocsCreate controlled documentation from engineering data and selected baselines, with links back to items.
REQ-042
appears in controlled documentation
appears in controlled documentation
Verify
TraceTestExecute test runs, record results and evidence, and report coverage connected to engineering items.
REQ-042
linked to verification activity
linked to verification activity
05 — Optional AI capability
AI assists the engineering model.
AI can operate against configured engineering context rather than inventing its own source of truth. Deterministic relationships remain inspectable, and human review remains authoritative.
AI proposesGenerates a proposed import, task, test or narrative where supported.
System checks where possibleDeterministic counts, statuses and links can be checked against recorded engineering data.
Human approvesPeople review interpretation and decide what becomes committed project data.
06 — Real product evidence
Follow one requirement through the work.
These are real product views from the repository. The shared REQ-042 example makes the intended relationship explicit: one recorded engineering model, different specialized views.
Requirement → implementation
TraceBoard connects a requirement to engineering work.
REQ-042 · payment timeout behavior
Implementation relationships
See engineering entities and their links together.
REQ-042 · linked work item
Verification
TraceTest records execution and coverage against the same requirement.
REQ-042 · verification result
Evidence → documentation
TraceDocs turns controlled engineering data into documents.
REQ-042 · documented evidence
07 — Engineering State
Know where the recorded model needs attention.
Engineering State is a deterministic, on-demand aggregate across compliance assessment, traceability, verification, risk, consistency, change impact and baseline readiness. It is calculated from recorded engineering facts and defined thresholds—not an AI opinion, certification score or release approval.
Controlled snapshots
Baselines capture a point in the engineering model for comparison, traceability and documentation. They help answer what changed without implying that the snapshot itself proves correctness.
Evidence with context
Recorded results, assessments, relationships and documents remain connected so teams can review the evidence behind a project state.
07 — Why existing tools struggle
Engineering truth is the system of record.
Excel, Jira and Confluence can each be useful. The difference is the underlying engineering model, not a claim that one general-purpose tool is simply “better.”
Flexible, but controlled engineering traceability and relationships are difficult to maintain manually.
Excellent for task and project management, but not designed as the engineering system of record.
Excellent documentation platform, but engineering verification and relationships are not its core model.
08 — Pricing
Published annual pricing.
Self-hosted tiers let you choose the suite scope that fits your team. Detailed feature coverage remains available below.
Trial
€0
30 days · up to 5 users · full current feature set.
Download trial kitStarter
€999 / year
Up to 5 users · TraceBoard.
Request activationProfessional
€2,490 / year
Up to 15 users · TraceBoard + TraceDocs.
Request activationTeam
€5,990 / year
Up to 40 users · full suite, TraceTest and SSO (OIDC).
Request activationBusiness (€11,990 / year, up to 100 users) and Enterprise custom tiers are also available. Contact sales.
Show feature coverage and tier detail
| Capability | Starter | Professional | Team | Business |
|---|---|---|---|---|
| Requirements, tasks, bugs, tests | ✓ | ✓ | ✓ | ✓ |
| Baselines and traceability | ✓ | ✓ | ✓ | ✓ |
| TraceDocs | — | ✓ | ✓ | ✓ |
| TraceTest execution and coverage | — | — | ✓ | ✓ |
| SSO (OIDC) | — | — | ✓ | ✓ |
09 — Deployment and control
Run it where your engineering data belongs.
Self-host the core suite on customer infrastructure. Local AI can keep model requests inside your network when configured that way; OIDC, remote Git and cloud LLMs require their external services.
Self-hosted / Docker
TraceBoard Suite runs as a Docker Compose stack with its own databases on your server or infrastructure. The 30-day trial downloads as a single zip: unzip it, run ./start.sh (Linux/macOS) or .\start.ps1 (Windows), and the suite is available at http://localhost. Docker Desktop or Docker Engine with Compose v2 is required.
Local operation
A local Ollama or OpenAI-compatible endpoint can support local AI operation. Air-gapped use depends on the configuration and integrations you select.
Specific data operations
Use supported JSON, CSV, XLSX, PDF and DOCX operations rather than assuming arbitrary full-fidelity interchange.
10 — FAQ
Questions teams ask first.
Do I need to follow a regulated process to use TraceBoard?
No. TraceBoard Suite works for any engineering team. Standards-aware capabilities are available when needed, but teams are not forced into a regulated workflow.
Is there process overhead for non-regulated teams?
There is no unnecessary process overhead. Teams can start with requirements and tasks and add risks, hazards, tests, baselines and evidence as their engineering needs grow.
Are compliance features hidden from non-regulated teams?
No. Capabilities such as baselines, traceability and evidence-linked verification are available to all users. They are not hidden behind a special compliance mode.
What is the difference between TraceBoard, TraceDocs and TraceTest?
TraceBoard structures engineering work, TraceDocs creates controlled documentation from engineering data and selected baselines, and TraceTest verifies through runs, results, evidence and coverage connected to engineering items.
What is Engineering State?
Engineering State is a deterministic aggregate of the project's recorded engineering model across compliance assessment, traceability, verification, risk, consistency, change impact and baseline readiness. It identifies where the recorded model needs attention; it is not certification or release approval.
Does TraceBoard Suite support air-gapped deployments?
The core suite can be self-hosted and local AI can run through a configured local endpoint. OIDC, remote Git integrations and cloud LLMs require connectivity to those external services.
How does AI fit into the system?
AI is optional. It can propose, analyze, generate, query, import or narrate within configured context; deterministic relationships remain inspectable, and a human decides what becomes committed engineering data.
11 — Get started
Give your engineering work one connected truth.
Start with the structure your team needs today. Add rigor as the work demands it.
The trial download is an evaluation build. For questions about information submitted through this website, trials, or support, contact [email protected]. Formal website privacy information and terms of service are not currently published.