I built a small Vue/Vite web app where roughly 60–120 users will log in, submit forms, and view their submitted information. About eight team members will use a NocoDB interface to manage the data. The prototype currently uses SQLite locally, but I'll need a hosted database for production. This is a volunteer project, and I'd like to give the organization a realistic monthly cost before moving it to Azure. Azure's pricing calculator has many products and options, so I'm not sure which services I actually need or how to estimate the required resources. What would be a sensible starting architecture and cost range?
5 Answers
For this number of users, traffic is probably very small. A basic Azure App Service plus a small managed PostgreSQL database could be under roughly $50 per month, depending on the region, backups, storage, and whether the services run continuously. Make sure to check the database pricing separately because it can cost more than the frontend.
If the Vue/Vite portion is just a client-side app, you can deploy the built HTML, CSS, and JavaScript files with Azure Static Web Apps. The free tier may be enough for the frontend at this usage level. You would still need separate services for authentication, your API or backend, and the database if the app stores data securely.
Before using the calculator, list the actual pieces you need: static frontend hosting, authentication, a backend or API, a production database, storage/backups, and possibly monitoring. Don’t choose products just because they appear in the calculator. For a small volunteer project, avoid overbuilding with containers, load balancers, or high-availability services unless you have a specific need for them.
You can also estimate this with a small virtual machine. Measure the prototype’s memory and CPU usage while sending representative requests, then add plenty of headroom. A single small VM would likely handle the workload, with extra costs for disk storage and bandwidth. For a simple application like this, a low-cost VPS in the $5–10 monthly range is often sufficient, though it requires you to manage updates, security, backups, and the database yourself.
User count alone isn’t the main pricing factor. The important questions are how often users submit or retrieve data, how much data is stored, how much bandwidth is used, and whether the services need to be available 24/7. Given your stated usage, start with the smallest practical tiers, set Azure budget alerts, and review actual CPU, memory, storage, and request metrics after launch. A reasonable initial planning figure would be around $10–50 per month, with the understanding that managed backups, authentication, and higher availability can increase it.
Testing on your development computer won’t give perfectly precise production numbers because background tasks and hardware differ. For a small app, exact benchmarking usually isn’t necessary; use the measurements as a rough guide, choose a modest instance with headroom, and monitor it after deployment.