What does Vellum actually do?
A lot of assistant products still behave like dressed-up chat windows. They can answer questions, but they do not really persist across the places where work happens, and they do not give much control over how much they can do once connected to real systems. Vellum is aimed at a more ambitious problem. The public product pages show an assistant with memory, shared memory, channels, email, calendar, browser use, workspace apps, and device clients across web, macOS, iOS, and CLI. That makes the product feel closer to an assistant operating layer than to a single interface for asking smarter questions.
The strongest signal on the site is not just capability, but control. Vellum publicly explains the difference between managed and self-hosted deployments, where secrets and files are stored, and how permission levels like strict, conservative, relaxed, and full access shape the assistant’s reach. That is important because it tells you the product expects real operational use, not only casual experimentation. Teams that care about trust boundaries can decide whether they want Vellum to stay more locked down or act more aggressively inside connected systems, which gives the platform a level of deployment maturity many assistant tools do not expose clearly.