Comment by diggan 11 hours ago
> And that as soon as migrations happen, your storage costs will balloon, so you need a billing strategy on launch.
Unless people somehow figure out a way of hosting stuff somewhere else than Amazon/$host_that_charges_per_mb_transit (Hint: they exist)
Considering it would have to be a lean operation (assuming bootstrapped), then figuring out basic stuff like "We don't want to pay per MB sent" should be a pretty high requirement.
Backup to Backblaze B2, or, depending on architecture, rely on their object storage for hot data (depending on data cache and tier requirements). They partner with Cloudflare for free egress (on the Backblaze side) of public content as well.
https://www.backblaze.com/cloud-storage/pricing
https://www.backblaze.com/blog/backblaze-and-cloudflare-part...
Which seems to be a fine fit for a project management SaaS solution. If you have an origin with non text content, you can front it with Fastly or pay Cloudflare something enterprisey (which you should be able to do once you have traction). Regardless, this is an inexpensive content distribution and object storage architecture available vs AWS egress costs.
In Europe. Hosting for North American customers is a completely different story.
Dont OVH and Hetzner offer this? If you dont like bare metal perhaps run Coolify for your vercel like platform?
I don't think you'd have to consider migration all the data from Pivotal, but lets assume 10% just in case? Lets say that's 100TB in total (on disk), which you could host with 10x storage boxes from Hetzner, 24 EUR each per month, so 240 EUR in total, which includes 10 unmetered connections (1 per box).
> I don't think you'd have to consider migration all the data from Pivotal...
I do. You might not have demands to migrate all data from all of your potential customers, but far, far more people than you might expect treat their issue tracking system as a system of record and external memory for a HUGE assortment of things.
One hugely (and obviously) useful query chain that such a system answers is "Hey, this customer problem sounds familiar. Did we investigate it before? Did we solve it? If so, how? If not, why not?". For long-running projects, it is impossible to select the correct 10% of data to retain to also retain the ability to reliably -er- service those query chains.
Obviously I meant 10% of all customers would hypothetically migrate from Pivotal to this new imaginary service, not that 10% of the data from each customer would be migrated... So 100% of the data migrated from 10% of the Pivotal user base, pretty generous assumptions I think.
> Obviously I meant...
Respectfully: if it was obvious, I wouldn't have come to the conclusion I did and written up what I wrote.
> So 100% of the data migrated from 10% of the Pivotal user base...
Yeah, maybe. I don't know how large the slice of the Pivotal Tracker userbase you'd be able to retain even if you had a perfect clone. I bet it would be notably larger than you imagine it would be... it's my understanding that it has some pretty rabid fans that used it.
What hosting providers would you recommend?