Introduction
Vicket is a whitelabel customer support platform. You ship components you own (React or Vue), installed via a CLI like shadcn/ui, and they talk to a hosted, multi-tenant backend that runs your tickets, workflows, and help center.
The product is built for SaaS teams that want a support surface matching their brand pixel for pixel without rebuilding ticketing from scratch, and for agencies running support for multiple client products from a single dashboard.
What you get
- A support page you actually own. The CLI scaffolds React or Vue components directly into your repo (Next.js and Nuxt included). No iframes, no foreign CSS, no runtime lock-in. Restyle, refactor, or fork: the code is yours.
- A hosted backend. We run Postgres, the API, the workflow engine, the auth layer, and the agent dashboard. You point the components at the API and forget the data plane exists.
- Workflows and a help center, included. Event-driven automations (assign, escalate, notify) plus published articles and FAQs that your support page renders without extra work.
How it fits together
Your users hit your site. Your support page (built from Vicket components) reads articles and submits tickets through a site-scoped publishable key. Agents work tickets from the hosted dashboard. Workflows fire on lifecycle events and notify your connected tools when something interesting happens.
Read architecture for the full picture, or skip to quickstart to ship a working support page in under ten minutes.
Where to go next
- Just want to install it? Start with quickstart.
- Evaluating the platform? Read architecture and roles-and-permissions.
- Already installed? Jump to configure-support-page or workflows.