Get started

Your first scene takes five minutes, and every later one follows the same steps.

1. Get access

We're running design-partner pilots. Get a demo — tell us the workflow you want off your team's plate, and we'll reach out as slots open. If you're an SAP team or a consultancy, mention it; those go to a faster track.

2. Pick a blueprint

Open the app, create a workspace, and pick a blueprint. A blueprint is a pre-built scene for a specific use case — invoice triage, deploy monitor, customer 360, SAP cross-system query. It bundles the right tools, assets, and a starting prompt.

If nothing fits exactly, start from a blank scene. The agent will ask what you're trying to do and propose tools.

3. Connect your tools

The blueprint will name what it needs — Gmail, GitHub, Slack, Postgres, an SAP tenant, whatever. Each one is OAuth or API key, one click. Credentials live in your workspace, not on a shared Daslab account. Revoke any time.

LLM access is managed by default — nothing to configure, and a hard spend cap protects you. On Enterprise, bring your own keys: Anthropic, OpenAI, OpenRouter, Bedrock, Gemini, SAP AI Core.

4. Ask

Type what you want. "Show me PRs needing review." "Pull this week's customer signups from Postgres and group by source." "Summarize this week's customer support email."

The agent picks tools, runs them, drafts the result. You see exactly what it called and what it got back. If it wants to write anywhere — update a Sheet, change a record, send a message — it stops and asks. You see the diff before approving.

5. Save it as a scene

Once the result looks right, save it. The conversation becomes a scene — a shared workspace your whole team sees, its cells refreshed every time someone opens it. Schedule it to re-run, send notifications, or trigger from events.

That's the whole loop: ask, run, approve, save.

What to do next

Updated 2026-07-18