Can we tweak the wording to clarify what we mean? We'll add examples, too. I really hate opaque pricing and wanted to make this as simple to understand as possible.
1000 req/s * 86400s * 30d / 1000 * 0.05 = 129600
It's only $129/mo if it's 0.05c and not $0.05, which is not what the website says.
1. This is our earliest launch. We're very expensive for 86mm requests per day right now. We have volume pricing planned but not rolled out. If you're interested, I'd suggest trying a low volume site to see how it feels and then get ahold of me to talk about volume pricing.
2. Our service is designed for "valuable" requests, not any ol' asset. API calls and pageviews are usually a good fit. Sustaining 1k "valuable" requests/s for a full month is pretty rare. I know you and other people on HN run that level of infrastructure, but our value prop for you won't be very high until we're more mature.
25 * 86400 * 30 * 0.05 / 1000 = $3,240
I'm legitimately going to be spending 5-10x as much for my loadbalancer as I am 2 Heroku dynos and a reasonable Heroku Postgres instance.
All I can say is that I'd recommend discounting your price by 5-10x to put it in reach. You don't want to be the biggest line item in someone's budget, you'll be the first to go.
Back in the early days of FullContact, we charged a _lot_ per record for our Person API. After a lot of feedback at SXSW Interactive, we announced a 50x price cut. I'm pretty sure that's the only reason our API took off as a business. We optimized on volume and made it cheap to sustain thousands of requests a second. Five years later, that's paid off for us quite well.
Hopefully if we get to be the biggest infrastructure charge in someone's budget, it'll be really hard to get rid of us.
5-10x discounts for volume probably aren't unreasonable.
Are you guys bootstrapped? Curious to hear more on that front. :)
We aren't bootstrapped, we raised a seed round. Turns out when you don't need money it's easy to get ...
I'm happy to give you all the gory details if you want to shoot me an email (mrkurt at gmail). I think we triggered the flamewar thing on HN so I can't respond here very fast.
What? Why would you raise seed if you don't need it?
Take money when you can get it, not when you need it.
We took investment for a few reasons. One is diversification, we can put our own money other places. More importantly, I think, is it's not weird when someone needs to get paid like it would be if we were personally funding the company.
And, honestly, we wanted to be able to move faster. We can try riskier things, be more generous with free plans, etc, etc.
I'd love to find out more about what you all use for this stuff. I'm not shocked we're more than Enterprise Cloudflare, primarily because we don't have an Enterprise product just yet.
If you're building a SaaS that's doing ~2.6mm pageviews per month, you've probably saved enough time using our features that $126 is nothing. The economics for a free service or media property are different, but we'll be valuable for different reasons too (and possibly even have a different pricing model for stuff like that).
We should _also_ document a policy on DOS stuff. We don't intend to run people out of money if they do get attacked. In fact, we have some ideas for middleware that would end requests early and not bill at all. Still, when we've done metered services in the past we were really generous with refunds / credits after bursts (which is basically what AWS et all do too).
This reminds me of Verizon .02 cents debacle from a while back.
1) The fact in a latter comment you seem to have priced yourself out of being unable to afford this service doesn't make it not worth while
2) I imagine if you're looking at 500k rps you probably qualify for an enterprise level plan where you'd have a sit down chat and negotiate terms rather than just extending the pricing linearly.
So as with all software, yes, you can roll it yourself with other things, if you assume your time is worth zero. But we all know that is not true.
When a service is 10x your entire AWS bill the metrics of "Is my time worth that?" shifts. This is like a $500 car wash. We do moderate traffic and the pricing would make it the highest cost besides labor.
The car detailing shop I go to, has 1 old guy who used to detail private jets, and 3 young "kids" who provide hands on labour.
This stuff may be 'a science', but as the saying goes... it ain't rocket science, just semi-skilled labour.
1000 request/s is $0.05/s. 86400s/day * 30 days * $0.05 -> $129.6K/30d. 1k req/s is not that uncommon either. And that's before 'paid middleware'!
APIs and sites that'd truly benefit from this are immediately priced out.
I see why you priced it the way you did (gotta start somewhere with such a large upfront investment if you're not using cloud capacity), but you aren't exactly going to get any large customers with numbers like that. Project it to when you have ~500k req/s going through your service (778M ARR!): you cannot expect to still be making $0.05/1000 requests.
To put it into perspective, costs to call S3 are 10x-100x cheaper (GETs are 0.004/10000, PUT/POST/LIST/COPY is 0.005/1000) and S3 arguably does a lot more per request.
I really want to like it. The service sounds _awesome_, don't get me wrong. I'm a huge nerd for smart loadbalancing. I've written more loadbalancing code than I care to admit, but the economics just aren't there for me to even consider adopting your service. It's a lot cheaper for me to keep a pool of nginx servers in AWS regions around the globe with pre-established TLS connections back to the home DCs for much of the benefit fly.io brings.