Enable
The enable command is used to enable features in a Vela project. It can be used to enable authentication, API access, S3 storage, SMTP email sending, teams, payments and more. You’ll be prompted for configuration options for each feature and the command will generate the necessary code.
Syntax
$ vela enable <feature>Features have dependencies on each other — enabling API keys, for example, needs both auth and the API first. Each page lists what it depends on. Anything enabled can be turned back off with vela disable.
In any SvelteKit project
ai, analytics, backend, cms, content-negotiation and i18n work in a project Vela did not create, such as one from sv create. They adapt to what the project has: no route groups, no shadcn-svelte, no test harness.
auth and blog generate shadcn-svelte pages, as does everything that builds on auth: api-keys, notifications, teams, payments and subscriptions. In a project without shadcn-svelte they are refused before anything is changed.
The PocketBase backend, hooks and data directory.
Authentication for your application.
REST API endpoints for your application.
API keys for your application's API.
S3 storage for file uploads.
SMTP email sending for your application.
An mdsvex blog with posts, tags and an RSS feed.
Serve the same route as HTML, Markdown or JSON.
Internationalization and locale-aware routing.
Team management for your application's users.
Payment processing with Stripe.
Subscription plans for your application.
In-app notifications with a bell dropdown.
Inline editing with an admin bar, served from the app itself.
Background workflows for a project created before they were built in.
Web analytics with Plausible, Google Analytics or PostHog.
AI chat with the AI SDK through Vercel AI Gateway, OpenAI or Anthropic.