Self-hosted vs cloud weave: which should you choose?
Compare control, operations and setup when choosing how to run weave.
What stays the same?
Both deployment choices use the weave repository. The product combines connected tables, documents and agent access. Choose the operating model after checking the features your workflow needs.
What do you operate when you self-host?
You choose the server and data location. Your team is responsible for deployment, updates, access configuration, backups and recovery checks. The MIT-licensed software is free; infrastructure and operating time still need a budget.
When does cloud make sense?
The hosted plan lets you use weave in a browser without running its server. Review the current plan on the weave page and test the workflow with non-sensitive sample data before migrating a workspace.
How should you plan a migration?
Inventory tables, documents, relationships and integrations. Validate an export and a restore, then test one workflow in the destination. Keep the original workspace available until the new one has been checked.