I’ve really enjoyed building on Fly.io, and now I want to share https://attainable.dev.
This is a year long journey that started as my way to learn more about Firecracker microVM, Go, and Svelte. Along the way I found Fly.io and haven’t looked back since.
I’d love feedback!
Interesting, good luck with it! Out of curiosity, who’s your target market?
Is there any mechanism for roles, so that users can see only their own records for some tables, or maybe only a class of records for some tables, etc.?
I personally find the pricing a bit surprising; anyone who can afford these costs would probably just build an API themselves.
Right now I think my target market is small to medium sized SaaS companies and front-end developers. I also think this targets anyone building systems for agentic architectures. I truly feel there is a wave of new API development coming to support new AI native initiatives.
I do have Teams for APIs on the roadmap. I don’t yet have plans to do deep OAuth type roles for data. I definitely have considered it, and I’ve got drafts of the resource spec for it. But it’s not something I intend to have soon - but likely later.
Thanks for the comment on pricing, I’m really trying to get a sense of value. The pricing is based on comparative API implementations. I considered everything from shared VPC hosting all the way to AWS (API Gateway, Lambda, etc) and this pricing becomes really competitive when you add in the “ownership” costs, the literal design/development/deployment/operations of doing it all yourself.
It depends, I suppose, if buyers think like this. Big companies who can afford your pricing will give work to their dev teams, and pre-funding tech startups will just rustle up something themselves, because “working for free” just costs the spare time of a founding engineer. Maybe there is a sweet spot of “recent funding, wants to spend money, no/limited engineering capacity”.
The other thing that comes to mind on record permissions is that without any permissions system at all, the API system can’t be used for user accounts. If the sales pitch is that one does not need a backend, one would need something like Supabase or Firebase to fill that gap.
Thanks for the comments on the record permissions. It’s given me food for thought. The comparison to Supabase is excellent. I think this is different because with Supabase you have to still do a bit of work to get the edge API from your instance and with this it’s just an POST to create a full API (database and all). But it’s a useful comparison. Thanks!