How it works

How a request in Slack becomes a finished change

You bring a problem to Velden in Slack. It confirms what you meant, makes the change in your existing code, and then ships it or hands it to an engineer, as your team decides.

01

Ask in Slack

Mention Velden or type /velden in the Slack thread, in plain words. Nobody has to write a ticket or say which file to open. The web app works as a fallback.

02

Velden confirms what you meant

You see the ask restated, the scope, what it will not touch, and how risky it is. If that is wrong, you stop it there.

03

It asks only what it can't work out

A few grouped product questions, and only when the answer cannot be worked out from your code and the thread.

04

It works in an isolated sandbox

Each task gets its own temporary sandbox and stays within the limits your engineers set. Anything outside those limits is blocked, and every step is logged.

05

Try the change in a preview

What changed, whether the checks passed, and a preview when your repo builds one, so you can click through the change before anyone ships it.

06

Decide what happens next

Velden then ships the change once a reviewer approves, or hands it to an engineer to review first. Your team decides which.

We work with a few teams at a time.

A pilot runs on your own repo and Slack, on real work from your backlog. Velden works with GitHub and Slack today. Tell us about your team and we'll set it up with you.

Request access