What hosting do you use?
I know that Fly.io is the recommended hosting for OpenSaas apps, but what hosting do you all use for your apps, and why?Anyone use Railway, DigitalOcean, Render, etc?
3 Replies
Hi @Kynetix. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources, Wasp supports deploying your full-stack applications to several hosting providers. Here's what I can tell you about the hosting options:
Officially Supported Providers
- Fly.io is the primary recommended provider with automated deployment through the Wasp CLI. It offers $5 free credit each month and allows deploying your entire app (server, client, and database) with a single command. Deploying with the Wasp CLI
- Railway is mentioned as "coming soon" for automated deployment through the CLI. However, there are already manual deployment instructions available for it. Deploying with the Wasp CLI
Other Supported Providers (Manual Deployment)
For manual deployment, Wasp provides step-by-step guides for:
- Netlify (primarily for client/frontend)
- Heroku (server and database, though no longer free)
- Railway (server, client, and database)
Deploying Manually
Community Usage
From the Discord conversations included in the knowledge sources:
- Many community members use Fly.io for the server/backend and Netlify for static content like blogs
- Some users have chosen Fly.io for simplicity, especially when not expecting heavy traffic
- There's mention of GCP (Google Cloud Platform) being used by some, though with noted cold start issues
It's worth noting that Wasp apps can technically be deployed anywhere that supports Node.js apps, static sites, and PostgreSQL databases. The documentation specifically mentions you can mix and match, such as "deploy your client on Netlify, the server on Fly.io, and the database on Neon."
The choice ultimately depends on your specific needs, expected traffic, and budget constraints.
I hope this helps with your hosting decision!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Kynetix, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
I use AWS. There is no specific reason for that. I'm just well-versed and fully immersed in the AWS ecosystem (for better or worse).
My deployment looks like this:
- RDS for Postgres
- ECS for server deployment
- Cloudflare pages for client deployment
- SES for email (this one is not natively supported in Wasp via API)
- Github actions for CI/CD to both ECS and Cloudflare
- Terraform for infrastructure
I'm sure other providers will also have similar features, but this is what I like most about AWS:
1. Fully private network with private subnets. You don't have to expose anything to the internet other than your load balancer's port 443.
2. Scalability and reliability of multi-az ECS deployment with Fargate. You never have to worry about failovers and hitting scale. Fargate spot can reduce the cost that no other provider can match.
3. RDS PITR, backups, encryption, etc. There is Aurora for better scalability, but it comes with a price tag. RDS serves me well for now.
4. SES is simple (as the name suggests) and cost-effective, although not feature-rich.
Works pretty well for me. I've been thinking about creating PR for a guide for this deployment with a sample app.
I've been thinking about creating PR for a guide for this deployment with a sample app.@saqib9810 please do, that'd be amazing!