Skip to content
Vibedata

Get started

Two ways to start

Your data engineering agent. It builds and maintains data pipelines on the platform you already run.

Read how it works
Two ways to start: a hosted sandbox, or a deployment from your cloud marketplace.

Which to start with

Try the sandbox

Hosted

Hosted and seeded on DuckDB, on our infrastructure. Sign in with GitHub and start.

Try the sandbox
The sandbox contains seeded data and an author-to-gate-to-ship loop.

Deploy from your cloud marketplace

Your subscription

Deployed into your own cloud subscription and billed through your marketplace account.

Deploy from Your Cloud Marketplace
Deploy from your cloud marketplace into your own cloud.

Side by side

A comparison of the two doors, row by row. Who it is for. Sandbox: Anyone evaluating, with nothing to install. Your cloud marketplace: A team ready to run it in its own cloud. First result. Sandbox: Your first session starts as soon as you sign in. Your cloud marketplace: Deploy from the marketplace listing into your subscription. What you need. Sandbox: A GitHub account with a verified email. Membership in a GitHub organization, for the demo restore. Your cloud marketplace: A subscription and permission to deploy a marketplace application. What you get. Sandbox: Seeded on DuckDB. Author a pipeline, watch it fail a gate, ship it when it passes. Your cloud marketplace: Vibedata running in your own cloud subscription, with your own keys and model endpoints. Your data. Sandbox: Seeded sample data only. The environment is shared, so production, personal and confidential data stay out of it. Your cloud marketplace: Your own data, under your own keys. Vibedata reads metadata, code and execution traces, never your rows. What it costs. Sandbox: Nothing. It runs on our infrastructure. Your cloud marketplace: Credit packs, billed through your marketplace account. A free Starter Pack comes with every new deployment.
The sandbox and your cloud marketplace, row by row

Both run the same loop; they differ in where it runs and who pays for the compute.

Two doors, the hosted sandbox on DuckDB with GitHub sign-in, and your cloud marketplace, deployed into your own subscription, lead to the same loop. You author a pipeline and it goes to a gate. If it fails, it goes back to the pipeline. If it passes, it ships.
Either door, one loop: author a pipeline, gate it, ship it once it passes

Choose a door above, or read how it works first.

Read how it works

Prefer to see it first? A founder walks you through it on a call.