Verus Ventures
Verus Ventures

The operating layer your business actually runs on.

The applications, workflows, reporting and approvals your teams work in every day — built for your business, over the systems you already run.

See how it works
A retained core system and three specialist systems meet the edges of the operating middle; the work between them runs in one field.

Keep the systems that work.Everything else lives in Habitat.

Habitat holds everything a piece of work runs on: the objects your business keeps, the connections into the systems that feed them, the permissions that decide who can see and change what, and where each value came from. Underneath sit the storage, the queues, the jobs that run overnight and the warehouse your reporting reads. Work starts at the part that is particular to you.

Everything under that work already stands, and most of what goes on top is drawn from an extensive catalog of parts already built and running. What gets built on it reaches from one step of a process to a whole system too specific to buy and too sensitive to send out.

Inside the platform

Habitat runs where you need it to run.

The platform stays the same. What changes is whether the tenant, cell and control plane are shared, dedicated, or inside your cloud.

Data
Users +
roles
Tenant
config
Database
Services +
jobs
Storage
Queues +
events
Cell
security
Admin +
control
Cloud
foundation

Your data is kept apart inside a shared cell we operate. Users, roles and tenant configuration remain specific to your tenant. The cell and control plane already exist, so no new cell or cloud foundation has to be stood up before the work starts.

Operated by Verus
Your tenant: Data, Users and roles, Tenant configuration. Shared Verus cell + cloud: Database, Services and jobs, Storage, Queues and eventing: task queues, topics and schedules, Cell security: service identities, WAF and subnet, Admin and control: identity, administration, provisioning, configuration registry, edge and delivery, Cloud foundation: account, billing, network, keys and secrets. Operations: Operated by Verus.

One ontology, assembled from every system.

Habitat resolves records from the systems you keep into shared entities, fields and relationships. Each source contributes what it knows. Connect another source, and the ontology grows without rebuilding the work already using it.

Systems of record

ERPCompany record
MESManufacturer record
License registryLicense record
Organization
  • Legal nameNorthwind Industries LLCERP authoritativeMES alternate
  • RegionERP
  • Company codeERP
  • Manufacturer codeMES
  • Production statusMES
  • License numberRegistry
  • License statusRegistry
Organization
Person
Work
Place
Document
Event
License
ERP and MES both supply Legal name. ERP is authoritative; the MES alternate remains traceable. One Organization definition resolves both records while retaining field provenance. Extend connects the License registry, adds its license fields and adds a related License object.

Every kind of work uses the same ontology.

Models

Analyses

Data products

Workflows

Applications

Agents

Models, analyses, data products, workflows, applications and agents all read the same ontology when they run.
How the model works

Selected insights.

View all insights