Your system architecture fits in three views.
You structure your requirements, model the system architecture and version the configuration. Pavot follows the complexity of your system and of the organisation building it, where legacy suites demand three tools and a six-figure licence.
From €500 / user / year · integrated, modular suite
Requirements in Excel, decisions in Slack, baselines by email.
Requirements, system architecture and configuration scatter across spreadsheets, chats, email threads, modelling exports and shared folders. Without a shared hierarchy or method, traceability cracks and external audit becomes a risk.
- A project lead cannot answer a simple question: what exactly is inside the system we are committing to?
- A requirement change starts an investigation across files, chats and diagrams before anyone can size the impact.
- Two teams can work from two different baselines for weeks before the mismatch appears in integration.
- Before an audit, engineers rebuild the proof chain by hand instead of reviewing the design: DO-178C, ISO 26262, EN 50128, IEC 62304, ECSS.
One tool: requirements, system architecture and configuration management.
Pavot brings the three systems-engineering disciplines together in one data model, then deploys them in your environment. You link a requirement to the function or component that satisfies it.
Requirements management
Needs, requirements, use cases, tests and risks in one linked, queryable repository.
System architecture
The CESAM views (operational, functional, constructional) and their interfaces, natively modelled.
Configuration management
Governed baselines, versions and change history, defensible in an internal or external audit.
Sovereign deployment
Self-hosted, down to isolated networks, with enterprise identity and an audit log.
The data model is the CESAM metamodel.
The repository natively carries the operational, functional and constructional views of the CESAM framework, with its traceability matrices and method-aware validation rules. Other tools, by contrast, impose a SysML adapter or generic fields to configure.
Needs→Functions→Solutions
No mapping. No synchronisation to maintain toward a modelling tool.
Built for environments that do not tolerate approximation.
Hosting, identity, audit and operational support are part of the buying decision. Project data stays in the customer plane.
Self-hosted by default
Pavot installs in your environment. Project data never leaves the perimeter, including on restricted-distribution networks.
- Offline activation, no outbound call
- Connected or fully isolated
Enterprise identity
Plug in your existing identity provider, or let Pavot manage it. Identity follows your rules, never the other way around.
- OIDC / Keycloak
- Roles & operational responsibility
Audit & baselines
Every change is traced. Baselines are governed, comparable and defensible in front of a prime-contractor or customer audit.
- Full audit log
- Baseline governance
Controlled AI access
A bounded, audited access surface for AI assistants, rather than raw access. AI assists without ever opening up the system.
- Bounded, revocable scope
- Every access is logged
Change one requirement, and the whole downstream stays reviewable.
A single edit surfaces the linked functions, interfaces and tests, and the missing review coverage, before the baseline moves.
Temperature tolerance at delivery · in scope
Thermal regulation and heating-state supervision · allocated
Heater / sensor / controller interface · linked
Heating and service temperature verification · planned, not approved
- The tolerance change affects the heating scenario and the service profile.
- A linked test remains planned but not approved for the next baseline.
- The completeness check flags a missing operational acceptance note.
Open, but under control.
Pavot integrates where it creates value: the right interface points, without diluting control of the system.
Database
A structured, queryable data foundation: a single source of truth for your requirements, instead of scattered files.
PostgreSQLReqIF & exports
Exchange your requirements in the standard ReqIF format, and export your matrices to the formats expected in review.
ReqIF · PDF · XLSXIdentity
Connect to your enterprise identity provider.
OIDC · KeycloakControlled AI access
A bounded, audited access surface for AI assistants, never raw access.
Audited accessAn integrated suite, within reach of SME budgets.
One tool, one data model, one audit log. Modular licensing: start with requirements management and extend.
A readable price, per user per year. You start on the requirements scope and extend at the pace of your projects.
- Evaluation: installable trial pack, offline, no commitment.
- Professional: requirements, CESAM system architecture and configuration management.
- Enterprise: isolated networks, enterprise identity, dedicated support and onboarding.
- Immediate start: no €100k platform to validate up front.
Validate the fit on a real engineering context.
The right entry point: an installable Pavot evaluation, then a technical exchange about your deployment, identity, traceability and governance constraints.