Now with self-hosted deployments

Your team already knows the answer.
Vellum just finds it.

One place to ask your team's knowledge — and get an answer, not ten tabs.

Start free Read the docs

vellum.example/app

Today

Q3 onboarding checklist Refund policy for EU VPN setup for contractors Where is the brand kit?Incident #4821 postmortem

Earlier

Payroll cutoff dates Office access badges API rate limits

You

How do I get a contractor set up on the VPN?

Contractors use the guest profile, not the staff one. Send them the invite from the admin panel — it expires in 24h. They install the client, sign in with the one-time code, and they're on the split-tunnel network automatically.

Sources: IT Handbook · “Contractor access”, #it-help thread (Aug 21)

You

Do they get access to the internal wiki too?

No — the guest profile only routes to the three services listed in the access policy (build server, ticketing, docs). Everything else is blocked at the gateway. If they need the wiki, an admin has to grant it per-person.

Source: Security Policy §4.2

Ask anything about your workspace…

↑

SOC 2 Type II · Self-hostable · Read-only connectors · Keyboard-first

Why teams switch

Built to answer, not to chat

Point it at your knowledge, ask in plain language, get a cited answer. Boring on purpose.

🔎

Answers with sources

Every reply cites the docs, threads and tickets it came from. No guessing where it got that.

🔌

Connects to your stack

Wiki, ticketing, code host, drive and chat — read-only, permission-aware. It only sees what the asker can see.

🛡️

Yours, and private

Self-host it or run it in your VPC. Data stays put; nothing trains anyone else's model.

⚡

Fast where it matters

Sub-second retrieval across millions of documents. Keyboard-first, no mouse required.

🧵

Threads that persist

Conversations are saved, searchable and shareable with a link your team can open.

🧩

Extensible

Write a connector in a few lines. Webhooks and a full API for everything the UI can do.