Current Limitations

Vecta is free during open beta and intentionally has a small feature set. Suggestions are welcome at support@vectaapp.com; features may be added later when they fit the product's simplicity and demand. These are current limitations, not promises about future work.

Limitation	What it means	Workaround
Restores are manual	The dashboard gives you a restic command; it does not restore files itself.	Follow Restoring Data.
No retention or prune policies	Repositories grow until you clean them up.	Run restic prune procedures yourself. See the restic documentation.
No excludes, tags, bandwidth limits, or advanced per-job options	Job configuration covers the core source, destination, and schedule.	Use tighter source paths or split work into multiple jobs.
Failure email only	There are no success or warning emails, digests, webhooks, or notification settings.	Safelist noreply@notifications.vectaapp.com and monitor the dashboard.
No signed-in password or email change	The dashboard supports password reset by email, not profile changes for these fields.	Use the password-reset flow.
UTC-only scheduling	There is no timezone setting.	Convert local times to UTC.
Run now is delayed	Run now waits for the agent's next check-in, usually about two minutes.	Confirm the agent is online.
Deletion erases snapshot records	Deleting a job or agent leaves repository data but removes Vecta's snapshot IDs and history.	Keep jobs, or keep your own snapshot list and use restic directly.
Only message tails are stored	Vecta does not retain full backup logs for each run.	Inspect /var/log/vecta-agent.log on the agent.
No database-aware backup type	Jobs back up files and paths.	Export database data to files before backing it up.
No teams, sharing, or dashboard API tokens	The account model is for an individual user.	Operate the account directly.
One destination per job	A job writes to one repository URL and destinations have no management page.	Create separate jobs for separate repositories.
Dialog-based management	Jobs and agents do not have dedicated detail pages.	Use the Jobs, Agents, and Logs views.
Individual runs have a duration cap	A run lasting roughly half a day can be terminated as failed.	Split large sources into multiple jobs.

What's next

Start with Getting Started, or read Troubleshooting for the operational effects of these limits.