Screvercommerce
Modules

Ten production modules. Pick what you ship.

Each module is independently deployable, exposes a typed API, and has its own admin UI surface. Mix and match — a destination might run only Commerce + Validator, an OTA might use Commerce + Concierge + Comms.

Module catalog

The full stack at a glance.

Click any tile to jump to its contract, metrics and use cases.

M1

Commerce Engine

Multi-provider catalog, cart and checkout.

RESTStripeTWINT
M2

Content Hub

Headless CMS with structured tourism content models.

GraphQLi18nRAG
M3

AI Concierge

Customer-facing trip planner that books.

MCPClaudeWSS
M4

Ops Copilot

Internal assistant with RAG over destination data.

pgvectorSSE
M5

Communication Hub

Journey-based multi-channel guest communication.

TwilioFCM
M6

Provider Portal

Self-service for service providers in a region.

RBACPDF
M7

Engagement & Gamification

Memories, badges, social — the post-experience layer.

OGBadges
M8

Mobile Apps

White-label iOS and Android apps.

RNOTA
M9

Point-of-Sale

Cash desk and sales terminals.

WebUSBESC/POS
M10

Validator

Offline-capable ticket and voucher validation.

Ed25519Offline
Cross-module example

One booking. Multiple modules. One coherent record.

A guest plans a ski day in chat, pays in-line, gets a wallet ticket, scans into the lift offline, and walks away with a shareable summit photo.

  1. STEP 01

    Concierge

    AI assembles cart via MCP tools

  2. STEP 02

    Commerce

    Pricing + payment intent

  3. STEP 03

    Workflow

    Rules eval (weather, occupancy)

  4. STEP 04

    Comms

    Confirmation + pre-stay journey

  5. STEP 05

    Validator

    Signed wallet token, offline scan

  6. STEP 06

    Engagement

    Scan triggers summit photo + badge

Each arrow above is a typed event on the internal bus. Replace any step with a partner service by implementing the same event contract — no platform changes required.

Module details

Open any module for capabilities, contract, metrics and real-world use cases.

Modules listed are currently shipping. Endpoints and payloads are illustrative of the public contract — the live OpenAPI / GraphQL schema is the source of truth (see API reference). Use cases describe real customer scenarios but specific tenant names are anonymized. Each module exposes the same typed shape regardless of tenant; vendor SDKs linked open in a new tab.

Ecosystem

Module marketplace.

Filter, browse and install modules from one workspace. Each module is a typed unit with its own admin UI and API.

app.screver.ch/platform/modules
PlatformModulesslug: modules
MK

Module marketplace

Commerce Engine

Cart, checkout, fare engine

Installed

Catalog

Tourism product types

Installed

Identity Hub

SwissPass, SwissID, OIDC

Installed

Pricing Rules

Dynamic + member pricing

Installed

Content Hub

Headless CMS, multi-locale

Installed

Ops Copilot

Internal RAG assistant

Available

Validator

Mobile gate validation

Installed

POS Terminal

Cash desk + Stripe Terminal

Available

Loyalty

Points + memberships

Available

Communications

Email · SMS · push

Installed

Reporting

Cantonal Meldewesen

Installed

Wallet

Apple/Google pass issuance

Available
Module marketplace · production modules

Keep reading

Architecture

How modules sit inside the layered runtime.

Open

AI capabilities

Concierge, Ops Copilot, autonomous agents, MCP.

Open

Commerce features

Carts, fare engine, entitlements, tax automation.

Open