Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
An open-source visual AI playground for building AI workflows by connecting nodes, powered by Vercel AI SDK Gateway.
Tersa is an open-source AI workflow canvas that lets you drag, drop, connect, and run nodes to build AI-powered workflows, powered by the Vercel AI SDK Gateway.
Tersa is a visual AI playground that runs as a web app built on Next.js 15 with React 19. It takes a visual node graph as input and executes it as an AI workflow, sending data through text, image, or video models from over 25 providers via the Vercel AI SDK Gateway. The project is created by Hayden Bleasel and published under the Vercel Labs organization on GitHub, released under the MIT license.
Tersa is for developers and builders who want to prototype AI workflows without writing custom orchestration code. AI engineers can quickly assemble multi-model pipelines to test provider performance. Product teams can use the visual canvas to communicate workflow logic to stakeholders. Indie hackers and educators can deploy Tersa as a free, open-source standalone tool for experiments or teaching.
To run Tersa locally, clone the repository from GitHub, install dependencies with pnpm, create a .env.local file with AI SDK Gateway credentials and any provider API keys, and start the dev server with pnpm dev. In the app, add nodes from a toolbar, connect them by dragging from outputs to inputs, select a model, and run the workflow to process data through the AI models.
Yes. Tersa is open-source and released under the MIT license, so you can use, modify, and distribute it freely. You only pay for the AI provider API usage when you run workflows with your own keys.
Tersa supports text, image, and video models from over 25 providers through the Vercel AI SDK Gateway. Exact provider availability depends on your AI SDK Gateway configuration and which API keys you have stored in your environment.
Yes, to run workflows you need AI SDK Gateway credentials and API keys for the providers you want to use. These are stored in a local .env.local file when running the app yourself.
Yes, Tersa automatically saves the canvas state to your browser's local storage, so your workflow persists across page reloads.
