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. |
| Retention choices are limited by plan | The current Free plan supports age-based retention up to 14 days, but not calendar keep rules. | Choose a supported age window, or manage repository cleanup with Restic. See the restic documentation. |
| No tags or bandwidth limits | Jobs support filesystem exclude patterns and basic retention, but not tags or bandwidth controls. | 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. |
| Native database backups support PostgreSQL only | PostgreSQL jobs create database-aware backups. Other database engines are not supported natively yet. | Export other databases to files with their own tools, then back up those files. See Database Backups and Hooks. |
| 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. |
| Snapshot history is job-scoped | The Snapshots page lists IDs reported by one job, not a full inventory of the repository. | Use restic snapshots on the agent machine to inspect the repository directly. |
| 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.