Seed your workspace with a Quick Start
A brand-new workspace has nothing in it. Orvanta Quick Starts is the gallery Orvanta shows you the moment a workspace is empty, so you can open something that already runs before you write anything yourself.
Requires: a Teams, Business, or Enterprise workspace. Trial and Solo workspaces don’t see this gallery.
Where it shows up
Section titled “Where it shows up”Open the Home page of an empty workspace (no scripts, flows, or apps yet). Instead of a blank page, you get a gallery with a few sections:
- Start here — a single guided reference flow that touches every pillar of the product in one run.
- Orvanta Quick Starts — five “Hello Orvanta” scripts, one per supported runtime: TypeScript, Python, SQL, Kotlin, and Bash.
- Orvanta Quick Starts — Flows — a minimal three-step DAG flow that chains scripts together.
- Other templates — a broader set of reference flows for common automation patterns.
Once the workspace has anything in it, this gallery is gone — it’s an empty-workspace feature, not a permanent template picker.
How it works
Section titled “How it works”Picking a card doesn’t create anything in your workspace by itself:
- Click a Quick Start card.
- For a script Quick Start, Orvanta opens the script editor with a pre-filled draft: the code, the input schema, and (where relevant) a dependency file are already in place.
- For the DAG flow Quick Start, Orvanta opens the flow builder with the three steps already wired together.
- Nothing is deployed yet. You can run the draft to see it work, edit it, or just look around — it’s saved to the workspace only when you explicitly save or deploy it, exactly like anything you build from scratch.
Everything in the gallery is bundled with Orvanta itself — picking a card never makes a network call to fetch template content, so this works the same on an egress-restricted, self-hosted instance as it does on Orvanta Cloud. (That is a property of the gallery, not of the instance: Orvanta still needs outbound access to the licence service — see Requirements.)
One Quick Start needs a little more than “click and run”: the SQL script asks you to pick (or create) a PostgreSQL resource before it can execute, since it’s the one Quick Start that talks to a real database. Every other Quick Start runs with no setup.
What next?
Section titled “What next?”- TypeScript Quick Start, Python Quick Start, SQL Quick Start, Kotlin Quick Start, Bash Quick Start — what each script demonstrates.
- Flow Quick Start — the DAG flow, step by step.
- Your first script — write one from scratch instead.
- Your first workflow — wire scripts into a flow from scratch.