03 / Develop

Develop

Everything for building on the platform — scaffold a new satellite, wire it to the Shell, and ship it.

Starting a new app? Go to Build a satellite — it's the one entry point: the five prerequisites (including the veni CLI) in Step 1, then the layer-by-layer walkthrough, then shipping. Get the platform itself running first with Get Started; skim Core concepts if the terms are new.

How-to

The end-to-end path, plus the single tasks you can jump to on their own.

Start here · the full pathBuild a satellite →

Set up, scaffold, run — then build a Calendar app end to end — a month view in the Shell, then an events API and database, who-can-edit, inviting people, org calendars, and shipping.

How-toRegister an app →

Add a running app to a Shell's launchpad — via the UI or the veni CLI, targeting Local or Cloud.

Reference

Look it up — commands, claims and code, not a walkthrough.

ReferenceThe veni CLI →

Every veni command and flag in one table. Install steps live with Veni builder, which serves it.

ReferenceWorking with the Shell →

The developer answers: exchange a token, what the token carries, call another app, authorization, and multi-tenancy — with real code.

ReferenceDeployment →

How the platform ships — Kubernetes, GitOps via ArgoCD, Kustomize overlays, and the feature → Dev → UAT → Prod promotion flow.

Projects

ProjectShell →

The host app. Start it locally and configure auth providers (Local / Google / Keycloak / OIDC).

ProjectVeni builder →

The dev-tooling app that serves the veni CLI and hosts the shared-UI component catalog.

Core concepts

The terms this section assumes — SCS, Module Federation, token exchange, guards, the event bus — are collected in a one-screen glossary, each linked to where it's used in depth. The full architectural model is in Platform architecture.

Start hereCore concepts →

Every term this section assumes, on one screen — the platform model, federation, auth, the backend stack, authorization and cross-system messaging.