Glossary

This is a reference, not something to read top to bottom. Skim it once so you know what's here, then come back when a term in another page doesn't click.

Terms are grouped by topic: the people first, then the product layers, then the app model, then how tenants and data work, then identity and the API.

People

End customer — The B2B company running its commerce business on revenexx (a Mittelstand wholesaler, distributor, or manufacturer). They work in Cockpit at app.revenexx.com. They don't write code; they configure.

Buyer — The B2B end customer who places orders in a storefront. They never see Cockpit.

Partner — Agencies and system integrators who deliver commerce projects for end customers. They build storefronts, write custom apps, set up integrations, and operate the platform on a customer's behalf. They publish public apps to the App Marketplace.

Developer — You. The person extending revenexx — at a partner, at revenexx, or on an end customer's own team. This documentation is written for you.

Product layers

Revenue Cloud — The complete revenexx B2B commerce platform.

Studios — The six product layers an end customer works in. Each Studio is a workspace for a different kind of work: Commerce Studio for selling, Experience Studio for storefronts, App Studio for apps, Integration Studio for workflows, Analytics Studio for dashboards, and AI Studio for agents and automation.

Commerce Studio — The core commerce capabilities — catalog, pricing, orders, checkout — delivered as apps.

Experience Studio — The storefront layer. Standard storefronts are built on Nuxt 4 with the Cover design system and visual page composition. Custom storefronts can be built against the platform's APIs and SDKs when the standard template doesn't fit.

App Studio — The runtime and marketplace for revenexx Apps. Each app is a self-contained module (data model, optional UI, optional code). Includes the core apps grouped into domains (Intelligence, Catalog, Commerce, Customer, Marketing, Sales) plus any custom apps you or partners build.

Integration Studio — Visual workflow automation for connecting Revenue Cloud to ERP, PIM, CRM, and other enterprise systems.

Analytics Studio — The dashboard layer for end customers: a self-service dashboard builder plus pre-built KPI dashboards over the tenant's own data.

Cockpit — The admin interface for end customers at app.revenexx.com. Its UI is composed from the extension points that installed apps declare.

AI Studio — The AI workspace: agents, insights, and automations over your tenant's data, growing in autonomy across four stages — assistant, copilot, autopilot, and agent teams. The AI Studio API is in progress.

App model

revenexx App — A self-contained commerce app. Defined by up to five declarative JSON files. Deployed once, available to every tenant, with each tenant's data kept separate.

manifest.json — App identity: name, vendor, version, dependencies, peer dependencies, permissions, policies, and events.

schema.json — The app's data model (its tables). Applied automatically when the app is installed; Git history provides the migration trail.

cockpit.json — Cockpit UI extension points: navigation items, views, widgets, and action buttons.

settings.json — Per-tenant and per-market configuration. Cockpit renders the settings forms automatically.

billing.json — Marketplace billing: free, paid (subscription plans), or included with a billing package.

Extension points — The declarative UI hooks in cockpit.json: navigation (sidebar items), views (full-page routes), widgets (dashboard cards), action_buttons (cross-app buttons).

Policies — The allowlist of platform capabilities an app requires. Apps get no access by default; the customer sees the requested policies at install time.

Peer dependencies — Apps that are required but not installed automatically. The customer installs them explicitly — useful when a dependency is paid or optional.

Lifecycle events — Platform events for an app's lifecycle (app.installed, app.uninstalled, app.upgraded, tenant.provisioned). Apps subscribe via events.listens.

Public App — An app available to every tenant through the App Marketplace. Requires billing.json. Built by revenexx or approved partners.

Private App — An app built for one specific customer. Appears only in that tenant's app list. No billing.json needed.

Included App — A core revenexx app bundled with the customer's billing package, activated automatically.

App Marketplace — The catalog where customers browse and install public apps.

Core apps — The revenexx-provided apps across the six domains: Intelligence, Catalog, Commerce, Customer, Marketing, Sales.

Market — A distinct business context within a tenant — a country, region, storefront, or any segmentation — managed by the markets core app.

Tenants and data

Organization — The customer's account: the legal and billing entity. Identified by org_id. Owns users and tenants.

Tenant — A workspace under an organization, identified by tenant_id. A tenant holds its own isolated application data. An organization can have several tenants (for example one per market or brand).

org_id — An immutable lowercase kebab-case slug (e.g. acme-holding) that identifies an organization. Unique across all organizations.

tenant_id — An immutable lowercase kebab-case slug (e.g. acme-eu) that identifies a tenant. You send it as the X-Revenexx-Tenant header.

Tenant scoping — Every request is scoped to one tenant, and data is kept separate per tenant automatically. You never write tenant filters yourself — include your tenant slug and you only ever see that tenant's data.

Identity and the API

ID — The revenexx identity service at id.revenexx.com. Customer and partner users sign in here; admin sign-in uses OpenID Connect.

Customers / auth — Buyer and customer accounts, reached through the API gateway. Buyer authentication for storefronts is separate from admin sign-in.

API gateway — The single entry point at api.revenexx.com. Every integration calls /v1/… here. The per-tenant OpenAPI document is at /v1/openapi.json.

Authentication — A request authenticates with either a bearer token (Authorization: Bearer <token>) or an API key (X-Revenexx-Api-Key), and always names its tenant with X-Revenexx-Tenant.

API key — A machine-to-machine credential, created in the customer's console, sent as X-Revenexx-Api-Key. Scoped to one tenant with its own permissions.

JWT — A bearer token that carries the user's identity and tenant. Issued when a user signs in through ID.

Search — Full-text and faceted search over a tenant's collections, with autocomplete and typo tolerance.

Storage — Per-tenant file storage. Upload through the API; serve and transform files from your own domain.

Messaging — Transactional and marketing email for a tenant.

Events — The platform's event stream. Emit business and platform events; react to them with webhooks.

Webhooks — Receive platform events at your own endpoint, and ingest signed events from external systems.

Acronyms