Apps mode
Apps is a mode of the Orkestia Cockpit window, next to Cockpit and Lumen. It answers "what apps do I have, are they up, and what do they use". An app is an Orkestia project: a sign-in app (Sign in with Orkestia), an app host project with a website, services and a database, or both. For the platform side read App Host and App enablement.
Apps used to be an item in the Cockpit menu. It now lives only here; the Cockpit menu's Run group has Runners and Connections.
Switch to Apps
| Where | What |
|---|---|
| Top right of the window | Cockpit | Apps | Lumen. The same control in all three modes |
| Command palette (⌘K) | Open Apps, New App…, Back to Cockpit; every app is also listed under Apps |
| Links elsewhere | Anything that used to open the Apps section opens this mode instead |
The mode is remembered across launches. A red number on the Apps button counts the apps that failed or need a look, so you see it from Cockpit or Lumen too.
The sidebar
The sidebar has the organization switcher on top, then All apps, then Your apps. The buttons next to Your apps read the apps again and start New App. With no apps the sidebar says so, or shows the error that stopped them loading.
Apps are in groups, each with a count, that fold when you click their name (Cockpit remembers which you folded):
| Group | Holds |
|---|---|
| Needs attention | Apps that failed or need a look, the failing ones first. The first problem shows under the name ("web keeps failing") |
| Hosted | Apps with a site or running services |
| Not hosted | Apps that sign people in with Orkestia but run somewhere else, or have not launched yet |
Staging and preview environments of an app are listed as small rows under it, not as apps of their own. With more than 6 apps a Find an app box appears. It matches every word you type against the name and the address, shows every match even in a folded group, and Esc clears it. Hover a row for the full name, the address and every reason.
All apps
The overview, across the whole width. The toolbar subtitle counts N hosted, N up, N failing and N need you. A banner names an app that needs a look, with the first reason. Cards are in two sections, each with the apps that need a look first and then by name:
| Section | Holds |
|---|---|
| Hosted on Orkestia | Apps with a site or running services |
| Not hosted here | Apps that sign people in with Orkestia but run somewhere else, or have not launched yet |
A card says what is wrong in a line under its name; an app with nothing wrong has no such line, because its dot and its live tag already say so. Right-click a card: Open, Health, People, Open in Browser, Copy Name, Copy App ID. A note says when health comes from stored state rather than a live check; opening an app checks it live.
New App (⌘N while in Apps mode) is for owners and admins only; other roles see the button disabled with the reason.
New App
| Choice | What you get |
|---|---|
| An app people sign in to | A website or app with Sign in with Orkestia, optionally with an address, services, a database and chat. Asks for a Name, an optional web address (https://<name>.app.orkestia.dev), and Who can sign in while it's in development (up to a small number of emails; opening it to everyone is a separate step at launch) |
| Services only | APIs, workers or jobs with no sign-in, under one project. Asks for a Project name |
The name of an app cannot be changed later. When it is created the sheet shows what was made (with Copy on values you need) and Next steps: Launch from GitHub…, Add a service… or Give it a web address…, and Open the App.
An app's page
Back with the chevron (All apps). Open the app opens its address in the browser. The Add button offers the changes that apply (below).
The toolbar has four groups, and a row under it names the views of the open group (a group with one view has no row). Opening a group returns to the view you last had open in it.
| Group | Views |
|---|---|
| Build | How it's built, Modules, Flags |
| Run | Health, Infrastructure, Environments (hosted apps) |
| People & data | People, Data, Files |
| Settings | Settings |
| View | For | Shows |
|---|---|---|
| How it's built | Every app | Status, address, people, this month's estimated cost, sign-in key, then the layers: the site and its releases, machines, services, the database, disks, workflows and the chat. Selecting one opens its facts: a service's address, image, copies, who can reach it (Publicly / Only inside the app), last deploy problem, and its Logs (with Before the last crash). Check again re-reads live state |
| Health | Every app | Health |
| Infrastructure | Every app | CPU, memory, compute, storage, network and metered usage: App infrastructure |
| People | Sign-in apps | People |
| Data | Sign-in apps | Data |
| Files | Sign-in apps | Files, Settings and Flags |
| Settings | Sign-in apps | Files, Settings and Flags |
| Environments | Hosted apps | App environments: staging and previews, turn on, promote, turn off |
| Modules | Sign-in apps | App modules |
| Flags | Sign-in apps | Files, Settings and Flags |
A services-only project has Build (How it's built) and Run (Health, Infrastructure and, when it is hosted, Environments).
Every change to an app goes through one sheet that says what will happen, what won't, whether it can be undone and which inputs it needs, with a destructive change asked for twice. Changes available include going back to an earlier release, serving or taking the site offline or redirecting it, restarting, scaling or deploying a new image of a service, removing a service, putting the machine to sleep or waking it, restarting the chat relay, adding or removing your own address, backing up a database or disk now, and marking an error fixed, ignored or reopened. Only owners and admins can change apps; others see the controls disabled with the reason.
Health
One tab per app, with panels that each stand on their own and say why when they cannot show something.
| Panel | Shows |
|---|---|
| Right now | Each service now: a sentence per process and the events behind it. checked ; the repeated-warning headline is shown under the process it came from |
| Errors | The app's open error groups from Lumen, with the count and when last seen. Mark this error as fixed, Ignore this error and Reopen this error are changes (with a root cause and fix recorded when you resolve) |
| Recent log lines | What the app and its services wrote, newest first (read a service's live output under How it's built) |
| Alerts | The alert rules for the app's project |
| Workflows | Runs of the workflows the app offers, named as people know them |
| Cost | What the app costs |
An app that does not send logs or errors to Orkestia says so in the panels instead of showing zeros.
When the app has a Lumen project, the top of the tab reads Open
People
For apps people sign in to.
| Panel | Shows |
|---|---|
| Counters | Seats used against the cap, and People with active and invited counts |
| People who sign in | Each person, their group (a selector) and a More menu. Search by email or group. A seat is taken the first time someone signs in, not when they're invited. Invite someone: name@company.com adds an email. A Seat pack selector buys more seats |
| AI members acting as users | Members of your team that answer in this app's chat. Manage them in Agents |
| Groups | What people in each group may do. Recommended groups can be added when there are none |
| Activity | What people did, filterable to one person (Show everyone clears it) |
Data
The app's tables, with Search N tables. Pick a table to read its records 50 at a time (Next), and open a record to see or edit it, or add a New record. Writes go through the same data API the app uses. Changing the structure of the tables (adding a table or a field) is not in the app; use the web console.
App chats and shared chats
Read your apps' chat spaces inside Orkestia Cockpit — add a chat by link or from your organization, notifications and unread counts, taking your member seat — and share assistant chats with the people in your organization
App infrastructure
What one app uses — CPU, memory, compute, storage, network and the month's metered usage — in the Infrastructure tab of Apps mode