ova

Approach

One backbone. A way of working that fits.

Every project on Nova is a combination of three independent choices. None of them is a slider that computes a price or an equity stake.

Approach

Three independent choices

How you build

Who develops, implements and hands over.

What you use

Which reusable technology and maintenance services you take.

How we partner

How development is paid or financed, and whether Nova participates.

Illustrative configurationNot a quote. Every combination is agreed per project.
Built byYour team + Nova
Your productYour product. Your brand.
  • Apps
  • Portals
  • Collaboration
Optional modules
  • Nova Memory
  • Nova Companion
  • Data connectors & context
Backbone foundationsNova Backbone
  • Access & permissions
  • Workflows & oversight
  • Admin & configuration
  • APIs & developer tools
How you build
Co-build
What you use
Core + modules
How we partner
Paid build

Approach

What that looks like for you

SME or operating companyOwn business-critical app · Core plus selected modules · own team, co-build or Nova · regular fee.
Product builderOwn product on the core · own team or co-build · custom work stays yours.
PartnerModules and Backbone for clients · certification · agreed distribution and support.
Founder ventureCo-founding team contribution · selection criteria · a fitting cash, equity or financing mix.
Private equity or portfolio companyA capped proof · three workstreams · follow-on after evidence and a joint decision.

Technology, execution and partnership are the same three choices for everyone. There is no separate contract type per audience.

From first scope to ongoing operation

From first scope to ongoing operation

Five delivery steps. These are not the three proof phases used with private equity.

  1. 01

    Scope

    A defined workflow, users and success criteria.

  2. 02

    Connect

    The systems and sources the product needs, connected in your environment.

  3. 03

    Build

    A working product on the Backbone, tested with users.

  4. 04

    Operate

    Agreed hosting, monitoring, fixes and support.

  5. 05

    Evolve

    Updates per subscription and further development by whoever you choose.

Approach

Ownership and continuity

01
What do I own?
Your custom code and product-specific development. Nova retains ownership of the shared Backbone and reusable modules.
02
Can my team continue independently?
The delivery should include the agreed code, documentation and deployment access, with lasting rights to the delivered Nova components. Updates and support depend on your subscription.
03
What happens if the company is sold?
The product and agreed usage rights should be transferable to the buyer. The buyer can choose whether to continue the update and support relationship.
Continue on your delivered version

Without an update subscription, you continue on the version delivered to you, with the agreed usage rights. That is not free access to the current Backbone.

Your own custom products may be developed broadly. Reselling the Nova core as competing infrastructure requires different rights. White-label and reseller rights are explicit additions; “Powered by Nova” is a technical endorsement, not a mandatory badge for every end customer.

Approach

What you pay for

  • 01

    Implementation or proof

    The agreed first build or proof.

  • 02

    Platform and modules

    Core licence and the modules you take.

  • 03

    Updates and service

    According to the package you choose.

  • 04

    Custom development

    Your own product, built by whoever you choose.

  • 05

    Partnership contribution

    Only where a risk-sharing or venture model is agreed.

Cloud, AI and external services are separate and paid in your own accounts.

One backbone. A way of working that fits.

Discuss your build