03 / Deploy

From managed PaaS to strict air-gap — without changing the cognitive contract

Compare Mentaview SaaS, PaaS, on-premises, embedded, OEM, SDK and air-gapped deployment profiles and their current readiness.

Current readiness is not uniform: PaaS/on-prem have the strongest runnable surface, Edge is a strict canary, and SaaS/OEM/mobile still have explicit productization gates.

01

Managed headless cognitive orchestration

PaaS

Controlled pilot

Value

Add governed cognition through authenticated APIs while keeping inference pools explicit and replaceable.

What exists

Tenant-aware HTTP runtime, PostgreSQL state, policy, routing, shared admission, turn-effect reconciliation and tenant-scoped normalized commercial-usage evidence with non-invoice readback.

Promotion gate

Server-wide adoption of provider idempotency, durable multi-instance conflict coordination, operator resolution for indeterminate dispatch, external tariff and invoice systems, high-throughput qualification, heterogeneous endpoints, SSO/SCIM and production SLOs.

02

Complete managed product experience

SaaS

Roadmap

Value

A turnkey service for teams that want Mentaview-operated lifecycle, quotas, support and control plane.

What exists

Reference Kubernetes manifests and the shared server runtime exist.

Promotion gate

Commercial control plane, tenant self-service, support SLOs, DR evidence and production qualification.

03

Customer-operated private runtime

On-premises

Controlled pilot

Value

Keep data, credentials and inference inside the customer's server, LAN or VPC boundary.

What exists

Core-only Compose, explicit optional inference, tenant auth, PostgreSQL RLS, atomic logical restore and a sealed physical backup/WAL exercise recovered to one measured LSN.

Promotion gate

Installer and upgrade qualification, encrypted off-site retention, scheduled recovery monitoring, production RPO/RTO, application reconciliation and full egress allowlisting.

04

Local cognition with no mandatory network

Embedded / Edge

Canary

Value

Run state, ingestion, retrieval and policy locally; add verified on-device inference only when the host chooses it.

What exists

Network-denied core-only restart plus a sealed content-addressed offline update and one-time device/manifest-bound rollback with exact state handoff.

Promotion gate

Physical-device evidence, hardware-rooted signing and identity, fleet rollout/revocation, power-loss, storage, RAM, latency, energy and packaging qualification.

05

Linked runtime for devices and appliances

OEM

Roadmap

Value

Embed a policy-governed cognitive layer behind host callbacks, selected accelerators and product-specific constraints.

What exists

Provider-neutral Rust traits, direct API boundaries and endpoint dispatcher.

Promotion gate

Stable ABI, integrator kit, compatibility matrix, signed packs and per-SKU assurance.

06

Build Mentaview into another product

SDK / Headless

Controlled pilot

Value

Consume cognition in-process for performance or through HTTP for remote clients without importing provider policy into the UI.

What exists

An unpublished Rust SDK v1 facade provides bounded in-process contracts plus a 14-test injectable synchronous network-transport contract with host-owned authentication references; it does not implement or qualify real HTTP.

Promotion gate

Real HTTP/TLS/DNS/egress qualification, timeout and cancellation enforcement, registry distribution, compatibility history, language bindings, streaming transports and stable ABI decisions.

Choose by boundary

The right deployment starts with who must control what.

Mentaview-operated lifecycle

PaaS now; complete managed SaaS after control-plane and operational gates.

Customer-operated data plane

On-premises with inference disabled or explicitly bound to local/private endpoints.

Network may disappear

Edge canary with local state, retrieval and an optional separately installed model pack.

Runtime inside another product

Unpublished in-process Rust SDK v1 today; registry distribution, compatibility history, language bindings and OEM kit through staged qualification.

A deliberate next step

Define the deployment envelope before selecting the model.

Residency, egress, restart, deletion, latency, memory and energy budgets should shape the profile — not the other way around.