- Sign in Open studio.daesha.dev and sign in with Google.
- Enter your code Codes look like DSHA-XXXXX-XXXXX-XXXXX-XXXXX and work once.
- Describe your app Pick App or Website, then tell Nautilus what to build.
- Review it Check the preview, open files, ask for changes.
- Publish Share a draft, then publish to name.daesha.dev.
DOCUMENTATION
Get from a code to a live app.
How to start in Studio, how apps you build can use AI and data, and the HTTP API behind Studio for scripts and the coming CLI.
QUICKSTART
Five steps from invite code to a published app.
AI inside your app
Turn on AI for the project in Studio, then use the SDK. Requests go through Daesha's proxy, so no key ever reaches the browser.
import { ai } from "@daesha/ai";
const reply = await ai.chat({
system: "You write short recipe ideas.",
messages: [{ role: "user", content: "Something with lemons" }]
});
console.log(reply);API REFERENCE
The Studio HTTP API.
Every request needs Authorization: Bearer with a personal access token
(they start with dsk_). Tokens act as you, so keep them private and
revoke them in Settings when you're done.
| Endpoint | Method | What it does |
|---|---|---|
/api/me | GET | Your account, plan and today's usage. |
/api/projects | GET | List projects you own or were shared. |
/api/projects | POST | Create a project from a name, template and optional files. |
/api/projects/:id/files | GET | List files with their text. |
/api/projects/:id/export | GET | Every file in the project, for a backup. |
/api/nautilus/step | POST | One Nautilus model step as a stream. Your client runs the tools and sends results back. |
/api/projects/:id/publish/start | POST | Start a draft or production publish, then upload files and finalize. |
The API is in alpha and may change. Daesha Wizard, the command line tool, will use these same endpoints.
STATUS
What to expect from an alpha.
No uptime promise
Studio is run by a small team and can go down. Export projects you care about.
Health check
studio.daesha.dev/api/health answers when the Studio API is up.
Published sites
Sites on name.daesha.dev are served separately from Studio, so they stay up while Studio changes.
Breaking changes
The API and SDKs may change during the alpha. Projects keep working after a change.
BUILD SOMETHING
Go from docs to a live app in one session.
Open Studio, describe what you want, and publish it when the preview looks right.