Novaryn

The platform

Anyone can demo an agent

Keeping one in production for a year is a different problem — tenant isolation, approval gates, budget caps, retries, evaluations and an audit trail. This is the layer that decides whether an automation survives contact with a real business.

The platform

What your automations actually run on

Dependencies point downward only, and every tier below is honestly labelled. Anyone can demo an agent; the tiers underneath are what decide whether it is still working in month nine.

01

Domain & experience

One data model behind the audit, the console and the admin — so an opportunity becomes a project without anything being re-entered.

  • Domain kernelLive

    one model, four surfaces

  • Scoring engineLive

    pure, tested, reproducible

  • Process libraryLive

    twelve costed processes

  • Design tokensLive

    OKLCH ramps, contrast solved

  • Theme engineLive

    admin-controlled, no rebuild

  • Component libraryBuilding

    token-driven primitives

02

Identity & commerce

The tenant boundary. Every row carries an organisation id, and row-level security enforces it a second time underneath the application.

  • AuthenticationSpecified

    sessions, OAuth, passkeys

  • Organisations & teamsSpecified

    tenancy boundary

  • RBACSpecified

    roles resolved server-side

  • Billing & subscriptionsSpecified

    Razorpay + Stripe

  • Usage meteringSpecified

    one indexed row per check

  • Audit logSpecified

    append-only, tamper-evident

03

Intelligence

No agent holds a provider key and no agent names a model. Both are why a price change or an outage is a config edit rather than a migration.

  • AI gatewaySpecified

    routing, retries, budget caps

  • Prompt registrySpecified

    versioned, evaluated

  • Vector storeSpecified

    pgvector, per-tenant scoped

  • Tool callingSpecified

    args re-authorised server-side

  • Agent runtimeSpecified

    durable, resumable

  • Human approvalSpecified

    risk-gated, expiring

  • EvaluationsSpecified

    regression gates in CI

04

Operations

Boring on purpose. The parts that decide whether an automation still works in month nine.

  • Background jobsSpecified

    queues, schedules, retries

  • Notifications & emailSpecified

    one template system

  • Feature flagsSpecified

    per-org rollout

  • File storageSpecified

    signed URLs only

  • SearchSpecified

    shared index contract

  • ObservabilitySpecified

    traces across the gateway

Next

Start with the number, not the architecture

None of this matters until you know what it is worth in your business. The scanner answers that in four minutes, and the answer is yours either way.