Should the browser screens and server deploy together?
Gravity’s documentation describes a unified Next.js app and a split Node.js server with a React browser app. If you choose the split setup, plan how to run both parts. Check the plan listing or ask the seller which architecture comes with the package before paying.
What are you buying and how many apps can you make?
The standard plans list source code and one year of updates. The license says one to three commercial applications depending on the plan. Confirm which project count applies and who can use the source, especially for client work.
What happens to your changes when a new version arrives?
The vendor distributes updates through a private repository. Keep your changes in your own Git workflow so a maintainer can compare new files with the copy you use. Track host and database settings separately from the source.
What would you need to move to a different host?
Draw one deployment for a fictional job board in the unified setup and two connected deployments in the split setup.
- Mark what runs whereLabel the screen, the server and the saved listings. On the split drawing show which browser app needs the server address.
- Plan a moveWrite which source, service settings and data would have to move. Circle the architecture your maintainer can operate.