Getting started

App Studio is where you build the platform's backend surface: an app owns its tables, serves its routes through the public gateway at api.revenexx.com, extends Cockpit with its own admin UI, and ships to a tenant — or to the Marketplace — with one deploy command.

Build your first app

There is one canonical walkthrough, and it lives in Getting Started: Your First App in 15 Minutes. It takes you from an empty directory to a live capability answering at api.revenexx.com — install the CLI, sign in, scaffold, deploy, verify. Start there; everything in this section assumes you have run it once.

Prefer to understand every file instead of scaffolding them? Build your first App builds the same app by hand, file by file.

Understand what you just built

App model explains the contract behind the scaffold: what each file is for, how declarations become tables and routes, where permissions and events fit, and where you actually write code. Read it after the walkthrough, before you grow the app.

Why apps cannot collide answers the question every developer from a plugin platform asks first: do I have to make sure my app does not overlap with other apps? No. The page explains the boundary that makes that true and where apps do legitimately meet.

What's in this section

• Data model — grow schema.json past one entity: columns, indexes, migrations, and the typed client.
• Your app's API — the router, custom routes CRUD cannot express, pagination, and the published OpenAPI contract.
• Platform services — entity access, events, scheduled work, and calling other apps.
• Admin UI — cockpit.json: navigation, views, and the local preview loop.
• Ship and operate — the manifest reference, deploying, billing, and verifying an app live.