ViberSpace does not hand you every surface at once. Each one appears in the command palette when you have done the thing that opens it — so the application you see is the part of it you are already using.
This page is the whole climb: seven levels, the nine surfaces the palette lists across them, and the single action that raises each one.
Split View and Debug exist but are not currently listed in the palette at any level.
Three things happen before the climb begins. None of them require you to read any code.
ViberSpace is invitation-only while teams are onboarded one at a time. An attempt to sign up without one is recorded, not granted.
There is no password. Enter the email your invitation was sent to, and a one-time code arrives there. That is the whole sign-in.
The dashboard asks what you want to build. Apps are kept pre-provisioned, so yours starts immediately rather than waiting to be created.
Inside an app there is no tab bar. The command palette is how you move, and it lists exactly the surfaces your level has opened.
On Windows and Linux, Ctrl replaces ⌘.
Each rung states the one action that raises you to it and what the palette lists once you are there. Every trigger sits on a surface the level before it opened, so the climb leads itself.
Every app starts here. Agent is a conversation: describe a change in plain language and it edits files in your repository and commits them to the dev branch, with a message and a diff you can read later.
WebView shows the app those commits produce, running.
Settings is the app's own record — its name, and what the agent has cost to run so far.
It is also the way through to the next rung: Settings links to Environments before the palette lists it.
Every app is created with a development environment. Environments is where you provision a production one alongside it, and where a custom domain is attached.
Each environment is a separate deployment with its own database, its own logs and its own URL.
Once production exists, Deploy is the surface that puts work into it: dev is merged into prod and pushed, and the deployment is recorded against the person who triggered it.
Nothing reaches production any other way. Promotion is an action a person takes.
Logs shows what a running environment is printing. You choose which environment you are reading — development or production — and they are genuinely separate.
Variables holds environment variables and secrets, set per environment.
History is the commit list: every change the agent made, in order, with the workflow runs that deployed them.
Database browses and edits the app's data directly — the tables the agent created, and the rows in them.
This is the last rung. From here the palette lists every surface the application has.
None of these surfaces sit on a sandbox. Everything the levels open is a view onto ordinary infrastructure that would keep working if ViberSpace stopped being part of the arrangement.
dev. Production is reached by merging it to prod, deliberately.
ViberSpace is invitation-only while we onboard teams one at a time. Tell us the app your team needs and how you work, and we will take it from there.
Already invited? Sign in with the email your invitation was sent to