Platform
One door. People, agents and integrations alike.
Authorization lives in exactly one place in Vusul. The interface, the Public API, the MCP server and every integration call the same services under the same policy. There is no separate “system” user and no shortcut for connectors.
MCP — 18 tools.
The server passes each call straight to the application services under the resolved user’s identity: the same path the REST controllers take — workspace policy, task visibility, audit attribution. Responses serialise the Public v1 resources, so what an agent sees is byte-identical to what a REST client sees.
The actor model.
Every integration install provisions its own service-account member, and every write a connector makes runs as that member through the normal services. Permissions, visibility and audit attribution apply unchanged. Plenty of tools let webhooks write in god mode; here there is no path around it.
Public API v1.
?fields= narrows the response, ?expand= embeds a related record. Both are strict allow-lists: an unknown value is not quietly ignored, it returns 400 — because a typo silently returning the raw record is the classic mistake integrations carry into production. Per-key hourly limits and X-RateLimit-* headers included.
Webhooks and OAuth apps.
Per-workspace subscriptions, automatic disabling after repeated failures, and client-secret rotation. Personal access tokens and OAuth apps go down the same authorization path.
It does not stop when the connection does.
Writes go into a queue in the browser’s durable storage; closing the tab — or the machine — does not lose them. The queue belongs to a person: a pending write is only sent when its own author signs back in. On a shared device that is a security property, not a convenience.
Clocks and SLAs.
An SLA clock can run inside business hours instead of 24/7. A two-hour target opened at 17:00 on Friday lands at 10:00 on Monday. The calendar is computed in the workspace’s own timezone and survives daylight-saving transitions.
Identity and governance.
SSO (OIDC and SAML), SAML single logout, SCIM user and group provisioning, directory-group-to-project membership, an audit log, and custom roles built from 21 permissions. Visibility permissions are locked at the base for security reasons and cannot be loosened by a custom role.
What we don’t do today.
We will shorten this list as the product moves; when we shorten it, the entry comes off this page.
- Email intake is not an SMTP server. Your provider receives the mail (SendGrid Inbound Parse, Mailgun Routes or a similar relay) and POSTs it to us already parsed. We deliberately do not run a mail server.
- Two of DORA’s four are proxies. Deployment frequency and change-failure rate are measured directly; lead time and MTTR are proxy calculations and are labelled as such in the interface.
- Module limits lock writes, not reads. On a plan that doesn’t include a module you cannot create new records in it (402) — but you keep reading and exporting what is already there, which is what "we don’t hold your data hostage" has to mean. The schedulers respect it too: a Free workspace generates no cycles and runs no SLA clocks.
- The desktop app is a developer preview. No packaged installer, no signing, no auto-update.
- Automated tests are server-side only. There are 594 on the server; there is no automated suite for the interface, which is verified by hand against 160 written scenarios.
- Two languages. Turkish and English. The layout groundwork for right-to-left exists, but no such locale has shipped.
- There is no paid subscription. Vusul is completely free right now — no checkout, no purchase step, and no end date on that. Paid plans will open later through Paddle; until then we open plan upgrades by hand, at no charge.