For app builders
Dev Studio Quick Start
Build an Ambivo app on your own computer, with Docker. For development partners, and for companies building their own apps.
Building for clients? Get approved first
To install apps in other companies, Ambivo must approve you as a development partner. Building apps for your own company needs no approval. To apply, write to dev-partner@ambivo.com.
Claude Code and the Ambivo dev kit build an Ambivo app for your clients or your own company, from a description or a brief. You check each step and own the code at the end. There are four ways to work. We recommend Docker.
| Way | Where it runs | Use it when |
|---|---|---|
| Docker | Your computer, in a container | Most of the time. Free. Dev Studio in your browser, VS Code, WebStorm or the terminal |
| Terminal | Your computer, with Claude Code installed | You already use Claude Code and Node. Free |
| Private hosted Dev Studio | A server for your team only, run by Ambivo | You want Ambivo to host Dev Studio for you. Paid. Coming in December 2026 |
| Shared hosted Dev Studio | Ambivo's shared server, in your browser | You want to try Dev Studio, or show a demo. It may be removed at any time |
Which way is for you
Build with Docker or in your terminal
Free. No approval needed. You install the app in your own company only. Each custom object the app creates counts toward your plan's limit on custom objects, the same as one you add in the CRM.
Ask to become a development partner first
Ambivo must approve you before you install apps in other companies. Write to dev-partner@ambivo.com.
On your computer
Docker or the terminal. Free.
Private hosted Dev Studio
A server for your team only, run by Ambivo. Paid. Coming in December 2026.
Shared hosted Dev Studio
For trying it out and for demos. It may be removed at any time. More
Two kinds of Ambivo app
| App extension | Standalone app | |
|---|---|---|
| What it is | New record types and fields inside an Ambivo app, such as the CRM | An app of its own, with its own screens and web address |
| Who makes it | Your client's admin, in the CRM: Settings > Objects > Create | You, in Dev Studio |
| Where it runs | Inside the CRM. Nothing to host | On a web host you choose |
| Pick it when | People already work in the CRM and need a few more record types | The app has its own screens and flow, for example warehouse staff on phones |
Dev Studio builds standalone apps only. Your app keeps its data in your client's Ambivo company, marked with your app's name. The CRM does not show those records.
Before you start
You need these things. Ask your Ambivo contact for the sandbox.
| You need | How you get it |
|---|---|
| Approval as a development partner | Write to dev-partner@ambivo.com and ask to join as a development partner. Ambivo tells you when you are approved. You do not need this to build apps for your own company. Each custom object those apps create counts toward your plan's limit on custom objects, the same as one you add in the CRM |
| A sandbox company | Send your work email. You get a set-password email at a plus address, for example priya+sandbox@yourcompany.com. It reaches your normal inbox. Set a password from the link |
| Docker Desktop | Free for personal use, and for companies with under 250 staff and under $10 million a year in revenue. Get it from docker.com. It runs on Mac, Windows and Linux. You need it for the Docker way only |
| A Claude plan or key | A Claude plan, such as Pro or Max, or an Anthropic API key from console.anthropic.com. You pay Anthropic for what Claude uses |
| Hosted Dev Studio access | Only for hosted Dev Studio. After approval, send your Ambivo contact your GitHub user name, or your company's GitHub organisation. Ambivo adds it to Dev Studio |
| Keys for hosted Dev Studio | Hosted Dev Studio has two coding assistants. Claude Code needs a Claude key: an Anthropic API key (sk-ant-api…) from console.anthropic.com, or a Claude subscription token (sk-ant-oat…) from claude setup-token. Codex needs an OpenAI API key (sk-…) from platform.openai.com. You pay Anthropic or OpenAI for what the assistant uses |
The sandbox is a test company for you alone. Your apps read and write sample data there, never in a client's company.
Build with Docker (recommended)
The Ambivo dev container has Node, Chromium, the dev kit and Dev Studio ready. On its first start, it downloads Claude Code from Anthropic. Codex works in the hosted Dev Studio only. It runs on your computer, with your own Claude plan. Your apps are saved in the folder you start it from.
On Windows PowerShell, use -v "${PWD}:/work" in place of -v "$PWD":/work, and type each command on one line.
First time only: sign in
- 1
Open a terminal in the folder you keep your apps in
mkdir ambivo-apps cd ambivo-apps - 2
Start the container and sign in to your sandbox
First it asks for your Ambivo sandbox email and password. Then Claude Code starts.docker run -it --rm \ -v ambivo-devkit-home:/home/node/.claude -v "$PWD":/work sgosain/ambivo-devkit - 3
Sign in to Claude in Claude Code
Claude Code asks you to sign in. Use your Claude account or API key. Then type/exit. Theambivo-devkit-homevolume keeps both sign-ins for the next start.
Check that it is ready. This lists what works and what to fix. It also checks that Anthropic accepts your Claude sign-in.
docker run --rm \
-v ambivo-devkit-home:/home/node/.claude -v "$PWD":/work \
sgosain/ambivo-devkit statusDev Studio shows the same list on the left. It starts no app until your Claude sign-in works.
Push to GitHub (optional). Sign in to GitHub once. It shows a code to enter at github.com/login/device:
docker run -it --rm \
-v ambivo-devkit-home:/home/node/.claude sgosain/ambivo-devkit githubThen Claude can push your app with git, and Dev Studio's Push to GitHub puts it on a new branch of a repository you pick. Both use your own GitHub account.
Then pick one way to work
A. Dev Studio in your browser. The same screens as hosted Dev Studio, on your own computer.
- 1
Start Dev Studio
Keepdocker run -d --name ambivo-devkit \ -p 127.0.0.1:4200:4200 -p 127.0.0.1:4300:4300 \ -v ambivo-devkit-home:/home/node/.claude -v "$PWD":/work sgosain/ambivo-devkit127.0.0.1in each-p, so only your computer can reach Dev Studio. - 2
Open Dev Studio with its link
Open the line that starts withdocker logs ambivo-devkithttp://localhost:4300/?token=. Your browser remembers it after that. The secret in the link keeps other programs out. - 3
Build the app
Click New app. Then go on as in steps 3 to 7 of Hosted Dev Studio. In step 4 there is no key to paste. Dev Studio uses your Claude sign-in. Each app gets its own folder in your apps folder. - 4
Stop and start it
Your apps stay in your folder when the container stops.docker stop ambivo-devkit docker start ambivo-devkit
On your computer, Dev Studio has no Share link and no Codex. One app's Preview runs at a time. Delete moves the app's folder to .devstudio-trash in your apps folder.
Use one way at a time. Stop the Dev Studio container before you open your apps folder in an IDE. Both use port 4300, and both keep their sign-ins and app list in the same ambivo-devkit-home volume.
B. VS Code, Cursor or WebStorm. Copy the .devcontainer folder of the dev kit into your apps folder. Download VS Code or WebStorm if you do not have one.
- 1
VS Code or Cursor
Install the Dev Containers extension. Open your apps folder and pick Reopen in Container. Dev Studio opens in your browser. If it does not, go to localhost:4300. - 2
WebStorm or another JetBrains IDE
Open.devcontainer/devcontainer.json. Click the container icon left of its first line, and pick Create Dev Container and Mount Sources. Then forward port 4300 in the IDE's ports list, and open localhost:4300. - 3
Claude Code in the IDE
Open a terminal in the IDE and runambivo-start. It starts Claude Code in your apps folder. Dev Studio keeps running beside it. Work on an app in one of them at a time.
Your apps folder is /work in the container. A change made in the IDE is also on your computer. Dev Studio lists only the apps made in Dev Studio. An app you make with Claude Code in the terminal is in your apps folder and in the IDE. It is not in Dev Studio's list.
Does localhost:4300 not load? Open a terminal in the IDE and run ambivo-start studio. Does Dev Studio ask for its link? Run this in the IDE's terminal and open the address it prints:
echo "http://localhost:4300/?token=$(cat ~/.claude/devstudio/access-token)"C. Claude Code in the terminal.
- 1
Start the container
Claude Code starts in your apps folder.docker run -it --rm -p 127.0.0.1:4200:4200 \ -v ambivo-devkit-home:/home/node/.claude -v "$PWD":/work sgosain/ambivo-devkit - 2
Build the app
Go on from step 4 of Build in your terminal without Docker. Ask Claude to start the app. If you start it yourself, runnpm start -- --host 0.0.0.0. Open localhost:4200.
Your sandbox sign-in lasts about a day. To sign in again, run this in a terminal on your computer:
docker run -it --rm \
-v ambivo-devkit-home:/home/node/.claude sgosain/ambivo-devkit loginUpdate to the newest version. Docker keeps using the copy it downloaded until you get a new one:
docker pull sgosain/ambivo-devkitThe dev kit README says how to build the image yourself.
Build in your terminal without Docker
Already use Claude Code and Node on your computer? You build the same app, with the same rules, and own the same code. Use any editor you like.
You need: your sandbox email and password, Node.js 20.19 or later, and Claude Code signed in. Ask dev-partner@ambivo.com for the sandbox. There is nothing else to download. Step 2 gets the dev kit from GitHub.
The dev kit is public at voicenectargit/ambivo-devkit. You need no GitHub account to use it. It belongs to Ambivo, Inc. You may use and change it to build apps on Ambivo. The terms are in its LICENSE file.
- 1
Open Claude Code in an empty folder
mkdir ~/ambivo-apps && cd ~/ambivo-apps claude - 2
Add the Ambivo dev kit
It teaches Claude the Ambivo API, the Ambivo screen style, and how your app signs people in. Type these in Claude Code:
If the first one fails, check the name and your internet connection. Still failing? Write to dev-partner@ambivo.com./plugin marketplace add voicenectargit/ambivo-devkit /plugin install ambivo-devkit@ambivo - 3
Sign the dev kit in to your sandbox
In a second terminal window, find the sign-in file, then runloginwith the path it prints:
Use your sandbox email and password. The sign-in lasts about a day.find ~/.claude/plugins -name ambivo-mcp.mjs -path '*ambivo-devkit*' node <path printed above> login - 4
Start your app
Back in Claude Code, say what the app does in a few words:/ambivo-new-app a stock count app for warehouse staff - 5
Answer the questions
The first asks if the app is for one company or several. Each question has a recommended answer. Replyuse your recommendations, or change the ones you want. - 6
Approve the brief
Claude writesdocs/APP_BRIEF.mdand waits for your yes. Read it first. A change costs least at this point. - 7
Run the app
In the second window:
Open localhost:4200 and sign in with your sandbox email and password. Ask Claude for changes in plain words.cd <your app folder> npm start - 8
Check it
It must finish with no errors before you hand the app over:npm run ambivo:check - 9
Package it
Ask Claude to bundle the app as a zip, or to push it to your GitHub. It builds the app and runs the check again first. Then set it up in the company it is for, as in Set the app up for your client.
Cursor or Codex? Clone the dev kit with git clone https://github.com/voicenectargit/ambivo-devkit, copy its plugins/ambivo-devkit/starter/ folder, and point your agent at AGENTS.md. It asks the same questions and writes the same brief. Run npm run ambivo:check yourself after each change.
Hosted Dev Studio
There are two hosted Dev Studios.
Private hosted Dev Studio. Ambivo runs a Dev Studio server for your team only. You pick its size and pay a fee. It is being built, and should be ready in December 2026. Write to dev-partner@ambivo.com to hear when it is ready.
Shared hosted Dev Studio, at devstudio.ambivo.com. One server that partners share. Ask your Ambivo contact for access.
The shared hosted Dev Studio is a trial, for demos
Ambivo may remove it at any time. Build your apps with Docker and the editor you prefer, such as VS Code or WebStorm. Keep each app's code in your GitHub or in a zip.
Build an app in the shared hosted Dev Studio
- 1
Sign in with GitHub
Open devstudio.ambivo.com and click Sign in with GitHub.
- 2
Sign in to your sandbox
Click Sign in to your Ambivo sandbox at the bottom left. Use your sandbox email and password. The assistant can then read your sandbox, set up your app's data and add sample records.
- 3
Describe the app
Click New app. Give it a name and say what it should do: who uses it and what they get done. Add your client's brief if you have one: PDF, Word, Markdown or text, up to 10 MB.
- 4
Pick the assistant and start
Pick Claude Code or Codex. Paste its key and click Start. You pick the assistant once, for the whole app.
- 5
Answer the questions
The assistant asks a few questions, each with a recommended answer. Click Use your recommendations, or answer them all in one message in the box at the bottom.
- 6
Try the app
Click Preview to try the app. It opens in a new tab. Sign in there with your sandbox email and password.
- 7
Ask for changes
Tell the assistant what to change, in plain words. It changes the app, and the Preview shows the result.
The first Preview installs the app's parts, so it can take a few minutes. The assistant never asks you to run commands.
Large apps: phases
An app with more than about 5 screens, or one built from a client's brief, is built in phases. You approve each phase before the next one starts.
- 1
Phase 0: brief and data model
The assistant reads the brief, asks its questions, and writes three files: the app brief, the data model and the phase plan. It builds no screens yet. Click Data model to see the app's data as a drawing.
- 2
Prototype (optional)
Every screen with sample data held in the app. Your client can click through it from a share link before anything is set up.
- 3
One phase per part of the app
Each phase ends with a short note of what it built and how to test it, and screenshots of its screens at desktop and phone width. Click Screens on the phase to see them.
- 4
Approve
Read the note, look at the screens, try it in the Preview, then click Approve this phase and Start phase on the next one.
To change something in a phase you approved, click Reopen on it.
Cost
Every message to the assistant is charged to your own key. The page shows what each step cost and the total for the app. A 15-phase lab app built with Claude Code from a two-page brief cost $76.85. Most phases cost $2 to $9, and the first prototype phase about $20.
A Codex app shows the tokens it used instead of dollars.
Set a limit before a large app:
- 1
Click Spending limit in the top bar.
- 2
Enter a limit in US dollars for each phase.
In an app without phases, the limit applies to each message.
- 3
Pick the model.
Sonnet is faster and cheaper for routine phases. Opus is the most capable, for hard ones.
When a phase reaches its limit, the assistant stops and the page says so. Raise the limit to carry on.
The spending limit and the model apply to Claude Code. A Codex app uses the limits set on your OpenAI key.
Hand the app to your client
| Button | What it does |
|---|---|
| Share | A link to the built app that you send your client. They sign in with an Ambivo account. Turn the link off at any time |
| User guide | The assistant writes a guide for the people who use the app and for the admin who sets it up, with screenshots, in plain words. Download gives one HTML file. Write it again after the app changes |
| Download zip | The app's code in one zip file. You pick one of two versions:
|
| Push to GitHub | The app's code on a new branch of a repository you choose |
Delete an app
Click Delete and pick one:
- Delete the app in Dev Studio. Its files, conversation, preview and share link go. What it made in your sandbox stays.
- Also remove what it made in my Ambivo sandbox. Dev Studio first lists everything that will go. Type the app's name to confirm. It removes the app's own data and the sample records, and touches only your sandbox.
It keeps products that have stock movements, and the movements themselves, because Ambivo keeps every movement. The list tells you what it kept and why.
Set the app up for your client
The app keeps its data in your client's Ambivo company. It needs no database or server of its own.
Before anyone uses it, the app is set up once in that company:
- 1
An admin of your client's company runs the install step.
It creates the app's custom objects in that company, for example Projects or Trials. They start empty. It changes nothing else.
- 2
Run it again after an update.
It is safe to run more than once. It brings the custom objects up to date.
- 3
One company at a time.
An app for several clients is set up once in each client's company.
The README file in the code lists the commands. It also says how to put the app online.
Good to know
- Sign-in. Your hosted Dev Studio sign-in lasts 8 hours and renews while you use the page, for up to 7 days. Your sandbox sign-in lasts about 24 hours. The bottom left shows when it ends. Your apps are kept either way.
- Messages while it works. You can send a message while the assistant is working. It waits and goes to the assistant when the current step ends. Up to 5 can wait.
- Idle apps. In hosted Dev Studio, an app nobody uses for 30 minutes is paused and its files are saved. It starts again on your next message or Preview.
- Your keys. In hosted Dev Studio, the bottom left has buttons to change or delete your Claude key and your OpenAI key.
- Help. Write to your Ambivo contact with the app's name and what you saw.
