VegaDūtaPlatform · Apps
App Studio: describe an app, get one you can run
App Studio builds an app from a description. You say what the app should do, the studio generates a multi-page app, and a live preview shows it running as it is built. You then change it by asking for the change in plain language.
The app does not need its own AI backend. You wire the agents and workflows you already have in VegaDūta behind named actions, and the published app calls them.
By the VegaDūta team · Last updated
In short
- App Studio on VegaDūta turns a plain-language description into a multi-page app with a live preview.
- A project can start from a Figma frame or an existing GitHub repository, and a bounded self-repair loop feeds build errors back to the model.
- Published apps can have their own end-user sign-in and call the owner's agents and workflows; custom domains are not served yet.
Start from a prompt, a design, or a repository
A project can begin three ways. Describe it in words, optionally with a sketch or screenshot as a design input. Import a Figma frame using your own Figma access token. Or import an existing GitHub repository, after which the studio shows when the branch has changed outside the studio and can pull those commits in.
A repair loop, and a database per project
When a generated change fails to build, the error is fed back to the model for a corrective pass, a fixed number of times, before the studio stops and shows you what went wrong. A project that needs data gets its own database schema with its own database role, so one project's credentials cannot read another's tables.
Publishing, sign-in, and disposable apps
A published app is reached by a link. It can run its own end-user accounts, with sign-up and login that are separate from your VegaDūta console users, and each action can be marked as requiring sign-in. Calls from the app run inside the owner's plan and budget. A project can also be created as disposable: it archives itself after a set time, 72 hours by default, unless you extend it or keep it.
What is not there yet
Custom domains do not serve apps yet. The studio can record a domain and verify that you own it, but published apps are reached through their VegaDūta link today. Phone app store listings are also your own step: the studio provides a readiness checklist, not a submission.
Frequently asked questions
Can VegaDūta build an app from a description?
Yes. App Studio generates a multi-page app from a plain-language description and shows a live preview. You refine it by describing changes.
Can I import a Figma design or an existing codebase?
Yes. A Figma frame can be imported with your own Figma access token, and a GitHub repository can be imported and kept in sync when the branch changes outside the studio.
Can users of my published app sign in?
Yes. A published app can have its own end-user accounts with sign-up and login. Those accounts belong to the app and are separate from VegaDūta console users.
Can I use my own domain for a published app?
Not yet. Domain ownership can be verified in the studio, but apps are not served on custom domains today. Published apps are reached through their VegaDūta link.
See it working in two minutes
The sandbox provisions a real tenant — describe an agent in one sentence and test it, no account, no card. Or browse ~90 industry workflow recipes to see what teams build.
