FAQ

Frequently asked questions

What Velden is, who it is for, and what you see before anything goes live.

About Velden

What is Velden?

A senior engineer for your whole company, working in Slack. You bring it a problem, a question or a vague idea, the way you would to a good engineer. Velden talks it through, works out what is needed, makes the change in your existing code and ships it once your team agrees.

Who is it for?

Companies with engineers, where there is more engineering work than time. People across the company bring Velden their problems directly. Engineering leaders set who may hand off work and how changes ship, and engineers work with Velden when they want to or when a change needs their review.

How is Velden different from other coding agents in Slack?

Velden follows every change through without anyone setting it up. It asks what it needs to know, says what it understood before it touches code and suggests a simpler way when there is one. Then it ships through your team's process, watches the result in production against what you asked for and comes back with how it went, all within the permissions of the person who asked.

What do you see?

First, Velden's understanding: your request in its own words, the scope, what won't change, the risk and how confident it is. Then a change you can check. Going live always needs a person to agree.

The work

What work is it good at?

Working out what a vague request needs, finding out why something broke or changed, reviewing code and proposing a plan, feature work, product fixes, and UI with backend changes. It works on the repositories you already have.

What should you not delegate yet?

Major migrations, security redesigns, deep infra, broad rewrites, and highly ambiguous multi-quarter work.

How long does a task take?

Small changes usually take a few minutes, and larger ones take longer. Velden posts in the thread when a change is ready for review.

Where does the change go?

Into a pull request on your GitHub repository. Then Velden does what you agree: it ships the change when someone with the right role says so, or an engineer reviews it first. Your team sets which.

Security and data

Which AI does Velden use?

The coding agent your team already uses, such as Claude Code or Codex, with your own contract with its provider. If you don't have one, Velden brings its own.

Where is our data stored?

Where you choose: the cloud and region that suit your company, for example the EU.

Which repositories does it work with?

Repositories on GitHub. You choose which ones Velden can see.

Getting started

How do I start?

Request access on the pilot page. We work with a few teams at a time, on their own repo and Slack, and set it up with you.

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