How much does it cost to keep a personal web app and its database online? Start with the app, database, and storage you need. Then add charges for usage above each included allowance. The examples below use US dollars before tax.
In this article
Decide what needs to run
A static portfolio can often be served from build output. An API or authenticated dashboard needs server-side processing. Budget separately for a database and persistent file storage when the app needs them.
Compare billing models
| Provider | What to check |
|---|---|
| Render | Workspace, app compute, database compute and disk, included usage |
| Railway | Subscription, included usage credit, and metered resources |
| Cloud Run | CPU and memory billing, request or instance settings, and a separate database |
| KamuiDash | Replica uptime, database tier, shared allowances, and overage rates |
Render and KamuiDash over 30 days
Each example runs one web app and one PostgreSQL database. We use Render Hobby with paid services and the KamuiDash personal plan. We use Render's published monthly prices and 720 hours of KamuiDash pricing. All metered usage falls within one billing month. The examples assume this app has the full usage allowances and exclude domains and object storage.
A small app for a few users
Assume 100,000 requests, 2 GB of outbound traffic, 30 minutes of build or deploy time, and two hours of database processing. Both providers add $0 in usage charges under these assumptions.
| Item | Render | KamuiDash |
|---|---|---|
| Web app | 512 MB, $7.00 | Nano, 256 MiB, $3.00 |
| PostgreSQL | $6.00 compute + $0.30 for 1 GB of disk | Nano, 3 GiB included, $6.00 |
| Total | $13.30 | $9.00 |
KamuiDash costs $4.30 less in this example if the app fits in 256 MiB. If it needs 512 MiB, Small plus Nano DB costs $11. Render pricing · Render billing guide · KamuiDash pricing
A growing app with at least 1 GB of app memory and 10 GB of database disk
Render's next paid web tier provides 2 GB. Its database disk is configured separately, so this example assumes 256 MB of database memory is sufficient. KamuiDash Medium provides 1 GiB for the app and 12 GiB of disk for the database.
Assume one million requests, 15 GB of billable outbound traffic, 100 minutes of build or deploy time as measured by each provider, and 24 hours of database processing.
| Item | Render | KamuiDash |
|---|---|---|
| Web app | 2 GB, $25.00 | Medium, 1 GiB, $10.00 |
| PostgreSQL | $6.00 compute + $3.00 for 10 GB of disk | Medium, 12 GiB included, $16.00 |
| One million requests | No separate per-request charge | 500,000 over the allowance, $1.00 |
| 15 GB outbound | 10 GB over, $1.50 | 10 GB over, $2.50 |
| 100 build or deploy minutes | Within 500 minutes, $0 | Within 100 minutes, $0 |
| 24 hours of database processing | No separate processing-time charge | Four hours over, $2.00 |
| Total | $35.50 | $31.50 |
KamuiDash costs $4.00 less under these assumptions. If Render Postgres also needs 1 GB of memory, its compute cost rises from $6 to $19 and the total becomes $48.50. Check CPU, connection limits and backups for your actual workload. Render pricing · Render compute plans · Render outbound bandwidth · Render build pipeline · Render billing guide · KamuiDash pricing
KamuiDash base fees
| Per replica or database for 30 days | Nano | Small | Medium | Large |
|---|---|---|---|---|
| App | $3 | $5 | $10 | $18 |
| PostgreSQL | $6 | $10 | $16 | $26 |
One Nano app and one Nano database cost $9. Adding a custom domain registration on KamuiDash brings that to $10, plus the registrar's separate fee. Two Nano app replicas and one Nano DB cost $12. Platform URLs are free. Base fees accrue while resources run and scale with uptime and replica count. For a full 31 days, multiply the 30-day price by 31/30 before rounding.
Usage allowances and other expenses
KamuiDash includes 500,000 requests, 5 GB of eligible outbound traffic and 100 deployment minutes per account per billing month. Overage rates are $2 per million requests, $0.25 per GB and $0.02 per minute. The KamuiDash billing month starts on the first day in Japan Standard Time. Database allowances apply per database and are prorated by active time. Nano includes five hours and Medium includes 20 hours per 30 days. Excess processing is $0.50 per hour. Processing sums the time spent executing SQL across connections, including waits during execution.
Object storage charges separately for storage and operations. At $0.025 per GB per month, 100 GB costs $2.50 for storage alone. Budget separately for external email, authentication, AI APIs, and domain registration.
Check capacity and revisit the estimate
Nano caps the app at 256 MiB and the database at 3 GiB with six app connections. Two processes with a pool of five connections each can exceed that limit. Review memory, connection pools, and peak traffic. A single replica can briefly stop during a restart, and the personal plan has no SLA.
After launch, compare the estimate with measured traffic, deployment time, and SQL processing. Usage notifications do not stop overage charges. The 30-day trial covers eligible app and database base fees, while usage overages, custom domains, and object storage can still incur charges. Apps that need no database can omit that fee. Keep persistent data off temporary disks. KamuiDash pricing and terms
KamuiDash is a Tokyo-region PaaS for publishing web applications through GitHub and AI integrations.