I've been working on this for over a year, and I'm really excited to finally push this out to a larger audience.
Something I've noticed pretty quickly is what I consider to be a "simple" idea is not as easy to translate to others. My product seems too simple, and I even made that a tag line. But I'm wondering if I'm missing something obvious. I'd love some feedback on whether I'm really communicating the idea well enough. My product allows you to deploy APIs within minutes. Any thoughts on how I could improve my message? https://attainable.dev
I'm a software engineer and I've got an idea that I'm ready to get feedback on. This is the first time I've shared my idea outside of close friends, and I'm excited to get thoughts from everyone. I'm building https://attainable.dev, the fastest and easiest way to design and deploy data APIs.
This has been a year long side-project that started as a way to spend my free time learning Firecracker microvm, Go, and Svelte. Shoutout to Fly.io. I built my idea on their platform and it was great! When I wrote the first iteration of this idea I really liked what I had. As I kept at it, weekends at a time, the more I felt this could be the idea for my own SaaS product that targets a real developer experience problem.
I've spent a lot of time in my career building APIs for platforms, web and mobile products, data foundations, and any number of projects like those. Each time I developed APIs I found myself wondering "can't we just write down the resources we want and hit deploy?" And now with the momentum around MCP and Agentic architectures, I keep seeing the need, and our industry is going in a direction that feels like we'll need to build and rebuild an incredible number of data APIs.
