DevTools

Add a browser debugger for your Velt integration.

A Chrome extension that surfaces your installation, data, live event stream, and mounted components, and switches between SDK versions, all in the browser.

// Stop guessing why a component will not render or an event will not fire.

Free extension. Works with your free API key.

3M+ comments created in products built on Velt.

Teams that integrated Velt faster with DevTools.Compare Velt

What it is

One extension, humans and agents.

Velt DevTools is a Chrome extension that debugs your Velt integration in the browser: it shows your installation overview, the data Velt has surfaced in your product, a live event stream, and the components you have mounted, and it switches between SDK versions to reproduce a fix. Agent activity appears in the same event stream as human activity, because an agent is a user with type agent, so you can watch what an agent did.

Velt DevTools: Eventsstreaming
EventsComponents
09:41:08Comment is Added
09:41:09Comment is AddedAGENT
09:41:19User Authenticated

one event stream, human and agent activity, live

How it works

Install, open, debug.

Install the extension, open your app with the SDK running, and pick a tab.

01Install the extension
Chrome Web Store
# install from the Chrome Web Store
# chromewebstore.google.com
# search: Velt DevTools
02Open your app and the panel
browser
// open your app with the Velt SDK running,
// then click the Velt DevTools extension icon
// in your browser toolbar to open the panel
03Pick a tab or switch SDK version
extension panel
// pick a tab: Overview, Data, Events, Components
// or switch the SDK version to reproduce a bug
// works in dev and production builds
With Velt

Nothing to add to your code.

The extension attaches to your running app and reads the Velt SDK live state, so there is nothing to add to your code beyond the SDK you already installed. It streams events as they fire, lists the Velt data surfaced in the page, locates and lets you interact with mounted components, and loads a different SDK version on demand to reproduce a bug or confirm a fix. It works wherever the SDK works: React, Next.js, Vue, Angular, and plain HTML.

no code changes, debug the same day

Build it yourself

Debugging by hand takes hours.

  • Console logs to find what the SDK can see
  • Network-tab archaeology to track what fired
  • Guessing which component is misbehaving
  • Version pinning to reproduce a regression
  • Support threads for what a panel would show instantly

DevTools replaces all of that with a live view of your installation, data, events, and components, so integration bugs surface in minutes, not a support thread. The extension is free.

Works with every Velt SDK target.

No per-framework setup. Install the extension, make sure the SDK is running, and open the panel.

npm i @veltdev/react

Works with every Velt SDK target

Install the extension, debug in minutes.

Free, no credit card.

Get Chrome Extension

Showcase

See exactly what Velt is doing.

Five panels in one extension, plus your agents in the same stream. Each is the live extension.

01overview

Installation overview

Key details about your Velt installation at a glance: API key, environment, config, and what is mounted. Confirm the SDK is wired correctly before you debug deeper.

02data

Data inspector

View all the Velt data surfaced in your product: comments, threads, users, documents, and locations, the same data your users see.

03events

Live event stream

Monitor every Velt event in real time, searchable and timestamped, so you see exactly what fired and in what order as you click through your app.

04components

Component inspector

Find and interact with the Velt components mounted in your product, so you can locate the one misbehaving and act on it directly.

05versions

SDK version switching

Switch between SDK versions right in the browser to reproduce a bug or confirm a fix, without changing your build.

06agent
09:41:08Comment is Addedhuman
09:41:09Comment is Addedagent
09:41:19User Authenticatedhuman

Agent activity, visible

Agent events stream beside human events, because an agent is a user with type agent, so you can watch and debug what an agent did, event by event.

We found the broken wire in minutes using DevTools, not a support thread.

Product Manager, HeyGen

Little big details

Every panel, every detail.

The showcase is the highlight reel. This is the index.

Installation health checkAPI key and environment displayDetected SDK versionConfig inspectionMounted components listComments and threads in the data tabUsers and online presence in the data tabDocuments and locations in the data tabLive event stream, real timeEvent search and filterEvent types: Document is Set, Comment is Added, Multi Cursor Initiated, New User Detected, User AuthenticatedEvent timestampsLocate and highlight mounted Velt componentsInteract with mounted components from the panelSwitch between SDK versions in the browserNo build change needed for version switchingAgent events in the same stream as human eventsWorks in development buildsWorks in production buildsReact, Next.js, Vue, Angular, and plain HTMLNo per-framework extension setupChrome Web Store distributionNo code changes beyond the SDK
Built for enterprise

Built for your customers' compliance.

Per-feature data providers keep content and PII on your infrastructure. SOC 2 Type II audited, HIPAA workloads supported, data residency options including the EU.

PILLAR 01 · DEPLOYMENT

Your data stays yours.

Velt stores minimal identifiers. Everything sensitive lives where you say it does.

▸ comments → your db
▸ recordings → your S3
▸ user PII → never leaves
PILLAR 02 · RELIABILITY

99.999% SLA

Reliability terms in writing for enterprise plans, with a public status page your team can watch.

trailing 90d100.000%
PILLAR 03 · GLOBAL

42 regions

Multi-region infrastructure with residency pinning, so review stays fast wherever your users work.

us-east, eu-west,
ap-south, +39 more
PILLAR 04 · COMPLIANCE

SOC 2 Type II.

The information your buyer's security team asks for, ready before they ask.

SOC 2 report under NDA
HIPAA BAA available
PEN TESTS regular

Proof

Teams that debugged faster.

Real names, real products.

Minutes, not hours

We found the integration bug in minutes with DevTools. Without it we would have spent a day in the console logs.
Product Manager, HeyGen

FAQ

Questions buyers and agents ask.

It is a Chrome extension that debugs your Velt integration in the browser: an installation overview, a data inspector, a live event stream, a component inspector, and SDK version switching, all reading your running app.

Add the Velt DevTools extension from the Chrome Web Store, open your app with the Velt SDK running, and open the extension panel. There is no code to add beyond the SDK.

It attaches to your running app in either, so you can inspect a development build or reproduce an issue against production.

Yes. The live event stream lists every Velt event in real time, searchable and timestamped, so you can watch exactly what fired and in what order as you use your app.

Yes. Switch between SDK versions in the browser to reproduce a bug or confirm a fix, without changing your build.

Yes. An agent is a user with type agent, so agent events appear in the same stream as human events. The extension is where you watch and debug what an agent did.

Every Velt SDK target: React, Next.js, Vue, Angular, and plain HTML. There is no per-framework setup for the extension.

You do not add anything to the app. Install the extension, make sure the Velt SDK is running in your React app, and open the panel; it reads the live SDK state.

The extension is free. It works with your free Velt API key, and Velt itself is priced on usage (monthly active documents), not per seat, with a free tier for development and early production.

Add a browser debugger for your Velt integration.

Free extension. Works with your free API key.