Laravel vapor costs $39 in the monthly plan and the Price does not include your AWS cloud costs.

ok, but something isnt clear.

on forge laravel, I can deploy one server for example 20$ / month and add all project in same server.

server 20$
- project 1
- project 2
- project 3
- project 4

if i get with vapor, you take 15$ by project. and each project cost 15$/lambda/month

- project 1 x 15$
- project 2 x 15$
- project 3 x 15$
- project 4 x 15$

39$ for Unlimited projects (vapor alone). But yes lambda is xx$ per project. Where do you get 15$ from?

@sylvain92 I mean... anyone using Vapor should probably be paying the yearly rate of $399 which breaks down to $33.25/mo. What you pay with Lambda is variable since your server auto-scales.

Keep in mind... what you get with Vapor for the cost would equate to a pretty robust DO server using Forge... so if your scale isn't insane and you want to keep costs low, sticking with Forge is the right move.

You can always change your deployment later as your company grows... unless you have some really strict zero down time SLA.

To figure out your Lambda cost AWS has a calculator for this...

https://aws.amazon.com/lambda/pricing/#Calculator

Another thing to keep in mind is that if you are running a SaaS app... scale should align with use. So, your cost should just equate to a small percent of what you're making from the app.

so, if nobody invocate project, then ican paid 0 ? because i use for many project, and all will not use every day

Also I think that there is a huge amount of free requests that you probably didn't consider. So maybe you can piggy back on that free tier for a while before you would have to pay anything.

@sylvain92 I agree with what @bugsysha is saying... but also... if you even have to think about cost and are going to be living in the free tier... you DO NOT need Vapor. The entire point of Vapor is to accommodate massive scale growth. Like MASSIVE. If you have to ask these questions... you very likely won't actually benefit from using it.

You can always migrate code from Forge to Vapor when it makes sense to do so.

of course, but there have some issue today.

forge laravel , work with project without laravel.

and in other hand, vapor, i have so much project, so it I paid when project are in stand by. it's pity

@sylvain92 I personally just use DigitalOcean, ServerPilot and deploy with Envoy scripts.

That way when I have projects that are just starting up... I can put them all on a single cheap server.

Basically paying $10/mo for DO, another $10/mo for ServerPilot. That's pretty much it. I pay for ServerPilot because I get unlimited SSLs with that. So all my projects, even demos have SSLs.

I use Google domains because they make it easy to do email forwarding accounts... which allows me to send and receive email on custom domains for free. This is a trick I just learned.

I may put together an article on how I do all of this as I find it fairly manageable and inexpensive.

what about price with database serveless ?

Serverless databases are required to be private. Creating a private database will automatically attach a NAT Gateway (~ / month) to your application's network if the network does not already have one.

I don't follow be question , the Vapor site Clearly states $39 per month and says

Unlimited projects, Unlimited deployments.

Then states;

Price does not include your AWS cloud costs.

So all the answers are right there on the Vapor site.

But unless you expect some major scaling, Forge would probably be great for you. 19.00 per month, But double check that price.

Of course that does not include your digital ocean, or whatever server cost.

Or digitalocean has tutorials. You can choose to go at it on your own.

Choice is completely yours.

i already have forge and do droplet. but what i wish with vapor. having a easy way to manage multi environnement in single yaml. and projet ares sorted by project. instead of by server.

Vapor

You pay for Vapor as a fixed price ($399 per year is cheaper, if you really plan to stick with it), which allows unlimited teams, projects and deployments.

Processing and Storage

• Lambda costs (probably negligible, but some optimisation will help you)
• S3 costs for storage
• You can use /tmp up to 500mb per request (but it vanishes at the end of the request, useful for processing files etc locally, but must be downloaded/swapped back to S3 afterwards).

Database

• NAT Gateway (about $32 per month per region, per project, I think)
• • private serverless MySQL/Postregsql costs (low)

OR

• public MySQL/Postgresql costs (about $15pm at the lowest, but can be shared between projects)

Caching

• DynamoDB is used by default, it's very cheap.
• But if you want Redis then you'll need to pay for the NAT Gateway again.

In summary:

If you have a lot of co-hosted projects, or at least one project at scale then the costs probably start to even out and make Vapor worthwhile on a purely price front. But, Vapor is much more scalable and can deal with peak demands without any worry on your part. There is a lot of powerful configuration taken care of for you, including setting up domains and CDNs per-deployment.

I don't really need it yet, I'm still developing the apps I want to deploy BUT I'd prefer to learn on the production environment rather than get everything nicely sorted for Forge/whatever and then find I have things to learn and fix once I switch to Vapor. A small area, for example, was switching out my upload implementation with a serverless-compatible one.

Plus it pays into the ecosystem in a few ways (Taylor is back on OSS, and Mohamed has started to join him in contributing public content).

In my current setup, without any real production deployments, I pay for Vapor, a public database server, S3 and Lamda costs. The public db server hosts all of my deployed databases for $15 a month, the other costs are usuall $1.5 a month. Grand total of $50 a month for numerous projects, with both staging and production URLs, automagic segregated S3 integration etc.