Developer Infrastructure

How to use Volvence infrastructure apps

These four apps are the core infrastructure surfaces developers use when integrating Volvence / DLaaS. Each app has one owner, a clear boundary, and a recommended integration path; product apps consume them instead of copying identity, rendering, visual asset, or DLaaS runtime state.

Get started Read docs

Tenant console + BFF proxy

DLaaS Portal

DLaaS Portal is the main developer entrypoint for DLaaS: provision an org, seal tenant credentials, try APIs, create and wake instances, and inspect usage, security, audit, and webhooks. The browser never receives tenant credentials; the Portal injects them server-side and audits each call.

Use it when

Use it first when connecting to DLaaS and confirming the tenant is ready.
Use it to try DLaaS HTTP APIs in the browser without exposing secrets.
Use it to inspect instances, usage, audit logs, webhooks, and security policies.

How to integrate

Finish org and tenant setup from Get started, then open the API console.
For server integrations, call through a Portal API key or session via `/api/proxy/dlaas/*`.
Before launch, check Usage, Security, Audit log, and webhook delivery records.

Boundary

Portal owns product identity, sealed tenant credentials, the BFF, billing mirrors, and audit. Cognition, memory, and runtime lifecycle truth remain in DLaaS / VolvenceZero.

Key configuration

PORTAL_PUBLIC_URLDLAAS_BASE_URLPORTAL_TENANT_SECRET_KEY

Get started API console Security & audit

Hosted identity + checkout + wallet

Volvence Accounts

Volvence Accounts is the shared identity, OAuth/OIDC, checkout, and wallet plane for consumer apps. Developers register apps, obtain client credentials, configure redirect URIs, and integrate checkout, wallet, entitlements, and signed webhooks here.

Use it when

Use it when your app needs hosted login instead of a local account system.
Use it for checkout, refunds, split settlement, wallet balances, or entitlement checks.
Use it to register an ecosystem app and manage redirect URIs and webhooks.

How to integrate

Create an app in the Accounts developer console and point callbacks to `/api/auth/callback/volvence-accounts` in your consumer app.
Configure `ACCOUNTS_BASE_URL`, `ACCOUNTS_CLIENT_ID`, and `ACCOUNTS_CLIENT_SECRET` in the consumer app.
Send payment and wallet actions through Accounts REST, then consume signed webhooks in the app.

Boundary

Accounts is the SSOT for identity, tokens, payment state, and wallet ledgers. Consumer apps keep product data and mirrors only; they do not copy identity or payment state machines.

Key configuration

ACCOUNTS_BASE_URLACCOUNTS_CLIENT_IDACCOUNTS_CLIENT_SECRET

Open Accounts Auth modes Get started

Digital-human and lipsync plane

Presence Service

Presence Service gives consumer apps digital-human sessions, speech transcription, TTS/visemes, performance plans, persona/consent registration, and rendering fallback. It turns digital-life output into visible, audible, auditable presence.

Use it when

Use it when a chat, companion, course, or character product needs an avatar, voice, and lipsync.
Use it when you need product-level control over high-fidelity rendering versus low-latency 3D or text fallback.
Use it to centralize likeness consent, session events, usage, and rendering webhooks.

How to integrate

Mark the consumer app with `presence: true` in `scripts/consumer-apps.json`; registration scripts issue credentials.
Use `@volvence/presence-client` with `PRESENCE_*` env and manage sessions with open / utter / close.
Set `PRESENCE_WIRING` and `PRESENCE_ENGINE_HINT` for the product, moving from shadow to active.

Boundary

Presence owns rendering sessions, persona/consent pointers, and performance plans. It does not own cognition, memory, model weights, or real asset bytes.

Key configuration

PRESENCE_BASE_URLPRESENCE_CLIENT_IDPRESENCE_CLIENT_SECRETPRESENCE_WIRINGPRESENCE_ENGINE_HINT

Open Presence Architecture docs Security center

Visual asset orchestration plane

Visual Service

Visual Service is the cross-app plane for visual asset registration, generation, storage, usage, and webhooks. Developers use it to idempotently ensure portraits, covers, scenes, props, video loops, and 3D models, then bridge ready assets into Presence.

Use it when

Use it when an app needs generated or reusable visual assets without owning its own generation queue and provider wiring.
Use it when pending, failed, or blocked assets still need renderable placeholders instead of breaking consumer pages.
Use it for shared library assets across apps and lifecycle tracking through webhook/SSE.

How to integrate

Mark the consumer app with `visual: true` in `scripts/consumer-apps.json`; registration scripts issue client credentials.
Call `ensureAsset` through `@volvence/visual-client`; `(appId, subjectRef, kind, variantKey)` gives idempotent dedupe.
Render with `placeholderUrl` first, then wait for ready through job status, SSE, or webhooks.

Boundary

Visual owns asset records, generation jobs, usage, and provider orchestration. Digital-human performance belongs to Presence; cognition and runtime remain in DLaaS / VolvenceZero.

Key configuration

VISUAL_BASE_URLVISUAL_CLIENT_IDVISUAL_CLIENT_SECRETVISUAL_WIRINGVISUAL_ENABLED_KINDS

Open Visual API overview API console

Recommended integration order

Start with Accounts for hosted login and app credentials, then use DLaaS Portal for tenant provisioning, API debugging, and audit. Add Presence Service when the product needs digital-human presentation, and Visual Service when it needs generated or shared visual assets. Runtime cognition, memory, and lifecycle truth stay in DLaaS / VolvenceZero.

Loading…

How to use Volvence infrastructure apps

Visual asset orchestration plane

Visual Service

Use it when

Use it when an app needs generated or reusable visual assets without owning its own generation queue and provider wiring.
Use it when pending, failed, or blocked assets still need renderable placeholders instead of breaking consumer pages.
Use it for shared library assets across apps and lifecycle tracking through webhook/SSE.

How to integrate

Mark the consumer app with `visual: true` in `scripts/consumer-apps.json`; registration scripts issue client credentials.
Call `ensureAsset` through `@volvence/visual-client`; `(appId, subjectRef, kind, variantKey)` gives idempotent dedupe.
Render with `placeholderUrl` first, then wait for ready through job status, SSE, or webhooks.

Boundary

Visual owns asset records, generation jobs, usage, and provider orchestration. Digital-human performance belongs to Presence; cognition and runtime remain in DLaaS / VolvenceZero.

Key configuration

VISUAL_BASE_URLVISUAL_CLIENT_IDVISUAL_CLIENT_SECRETVISUAL_WIRINGVISUAL_ENABLED_KINDS

Open Visual API overview API console

Recommended integration order