Nova
Establish shared ownership, work records, workflow and planning visibility.
- Work and issue tracking
- Team workspaces and statuses
- Planning visibility
- Lightweight AI assistance
From work tracking to engineering lifecycle management.
Progress from work tracking and shared knowledge to requirements, verification, service and enterprise ecosystem management through cumulative Nova-to-Cosmos packages. Select the scope and deployment model your organization needs.
Where should you begin?
Choose your broadest goal. This suggests a starting scope for evaluation, rather than a price quote.
Compare package scope
Each higher package includes the package below. The table shows where the listed scope becomes established. Nova also supports basic requirements work; governance depth grows with the package.
On narrow screens, scroll the table horizontally.
| Scope | Nova | Orbit | Zenith | Apex | Helios | Cosmos |
|---|---|---|---|---|---|---|
| Work, issues and team planning | Included | Included | Included | Included | Included | Included |
| Shared knowledge and broader requirements management | — | Included | Included | Included | Included | Included |
| Structured specifications and architecture traceability | — | — | Included | Included | Included | Included |
| Verification and evidence preparation | — | — | Included | Included | Included | Included |
| Governed readiness and acceptance | — | — | — | Included | Included | Included |
| Runtime, reporting and service continuity | — | — | — | — | Included | Included |
| Commercial scope and partner ecosystem | — | — | — | — | — | Included |
Proposal and licensing questions
What determines the proposal?
Selected capabilities, internal and external participants, workspaces, deployment, integrations and service needs define the evaluation. Identify the expected usage before agreeing license and operating terms.
What about AI and consumption?
Model routes, your own provider credentials or local models affect operating costs. Where applicable, storage, API and AI usage limits, warnings and overage behavior are agreed explicitly. A package name is not an unlimited-usage promise.
Are migration and support included?
Data migration, connector work, training and ongoing support are scoped separately in the proposal. Define responsibilities, support hours, acceptance criteria and recovery objectives alongside the deployment model.
Can the scope grow later?
Packages are cumulative. Begin with the required capability breadth and extend it as your operating model grows. Commercial terms, renewal, usage and deployment changes are reviewed together; no public fixed price or universal service level is implied.
Explore the six packages in detail
Orbit
Extend managed work with a connected knowledge and collaboration environment.
- Everything in Nova
- Collaborative knowledge spaces
- Wiki and working documentation
- Team context and shared memory
Zenith
Turn shared documentation into governed requirements and specification.
- Everything in Orbit
- Structured specifications
- Governed documents and requirements
- Traceability foundations
Apex
Connect controlled delivery with proof, governance and release readiness.
- Everything in Zenith
- Governance controls
- Evidence and proof records
- Readiness and delivery discipline
Helios
Carry delivery governance into runtime, reporting and customer service.
- Everything in Apex
- Runtime visibility and reporting
- Customer service continuity
- Reliability-oriented oversight
Cosmos
Extend the operating model across commercial commitments and organizational boundaries.
- Everything in Helios
- Commercial and contractual scope
- Partner and ecosystem collaboration
- Broad enterprise lifecycle governance
Evaluate package, commercial plan and deployment together.
Packages define capability breadth, and each higher package includes the package below. Commercial plans govern usage, licensing and operating terms. SaaS, private cloud and isolated deployment choices define data flows, integrations and shared responsibility.
Begin with a real delivery scenario. Review requirements, decisions, evidence, customer acceptance and operational scope together to select the appropriate package and operating model.
Deployment modelsMOVE FORWARD WITH CLARITY
See your own lifecycle in Velocize.
Bring a project, a changed requirement or a release decision. In a tailored demonstration, follow its plan, engineering work, AI contributions and acceptance evidence with your team.
Talk to an expert