Orkestia
Blog
Cockpit app

First run and onboarding

What the Cockpit app asks on a first sign-in, in order. Create the workspace, pay for the platform plan inside the window, connect GitHub or an AI provider, then enter the cockpit. What happens when billing is down and how to reopen onboarding

After you sign in the app decides between the cockpit and a full-screen onboarding chat. It shows the chat while your account has no organization, while the organization has no active plan, and, once after paying, for a short setup card.

sign in → no organization?  → 1. Create the workspace
        → no active plan?   → 2. Pay for the platform plan
        → just subscribed?  → 3. Set up GitHub or an AI provider (skippable)
        → otherwise         → Overview

A Sign out link stays in the header of every step.

1. Create the workspace

The chat checks your account, then greets you and proposes a workspace with one card.

FieldNotes
Workspace nameSuggested from your email: the part before @, without a +tag, split on ., _ or - and title-cased. joana.silva+ads@gmail.com becomes Joana Silva. Change it freely
Domain (optional)Leave empty if you have none

Choose Create my workspace. The assistant only proposes the card. The organization is created by the user.onboarding workflow, run with your own token, and it moves to its create_organization step only when you approve. If the run fails, the card stays and shows the platform's message so you can try again.

When the workspace exists the app reloads your account. If the account does not show it yet, the chat says Your workspace was created, but this account does not show it yet. Wait a moment and it checks again.

2. Pay for the platform plan

An organization with no active plan stays here. You pay inside this window: Continue to payment opens an embedded Stripe Checkout form.

  • The plan and price come from the platform's catalog. The app does not choose a price of its own. If the catalog offers none, you see No price is available for this plan yet.
  • The session is for one user seat.
  • Coupons: choose Add promotion code on the form (Adicionar código promocional if the form is in Portuguese) and check that the discount is in the total before you pay. If the code is missing or rejected, don't pay: write to hello@orkestia.dev.
  • The agent never charges. The payment is between you and Stripe.

After the form completes, the card reads Waiting for Stripe to confirm the subscription and checks the catalog every 3 seconds. A plan counts as active when its status is active or trialing. When it is, the card turns to Subscription is active and moves on.

If three minutes pass without confirmation, the card adds: Stripe has not confirmed the subscription yet. If you already paid, wait a moment or write to hello@orkestia.dev. Keep the window open; it keeps looking.

Organizations that already have a plan skip this step. Existing customers who sign in on a new computer land on Overview.

3. Set up (optional)

Once the plan is active the chat offers two starting points. Pick one, or leave both for later.

PathWhat it doesDone when
GitHub runnersConnect GitHub opens GitHub's install page in your browser. The card checks for a connection every 4 seconds, for up to 10 minutesThe organization has a live GitHub connection (github or github-app, not revoked or expired)
An agentic companyConnect an AI provider: choose OpenAI, Anthropic or Mistral, paste an API key and a modelThe organization has an AI provider configuration

For the AI provider the app first sets up a connection with the base URL of the chosen provider, then makes it the organization's default AI profile with your model. The key is stored by the platform and is not kept in the app after the call. Anthropic and Mistral go through their OpenAI-compatible endpoints.

The second step of each path (Create a runner group, Hire the first actor) shows as blocked with This step isn't in the app yet. Do those in the console or in the Cockpit views afterwards: Runners, Hire an actor.

A step that fails keeps its message and can be tried again. If the app cannot read whether a step is done, it says Could not check this step. and offers Try again; it never guesses.

Finish (or Do this later when nothing is done yet) opens the cockpit. That organization is not brought back to setup on later launches.

Reopen onboarding

Settings › AI tools › Open onboarding chat shows the chat again for the current organization: the payment step if the plan is not active, otherwise the setup card. Quit without choosing Finish and an existing customer lands on the cockpit again at the next launch.

When billing is down

A billing outage must not lock out someone who already pays. The rule is:

The plan check saysThe app
Active or trialing planOpens the cockpit (or the setup card once, right after paying)
No active subscription or authentication requiredStays on the payment step
Any other error (timeout, 5xx)Opens the cockpit

Right after you create a workspace, a failed plan check is treated the other way: you stay on the payment step, because a brand-new organization has no plan yet.

Where onboarding keeps its state

WhatWhere
That an organization still owes the setup card, or skipped itThis computer's app storage, per organization (cockpit.onboarding.setup). The cache list in About does not show or clear this entry
The workspace, the plan, GitHub and the AI providerThe platform

Next: Navigation and shortcuts.