That's exactly what we're doing next. Now that we have control over the content we're building some agents to promote and expand our reach with the content. It's all super easy and we're not sitting behind people that slow the process down.
It's not a "pivot" in the traditional sense. But yeah, building companies is probably one of the hardest things one can do. We still run https://release.com and https://release.ai is built on the same platform.
It would be hard to count. Basically every customer we had on Release 1.0 was an iteration towards this. If you go to https://release.com it's there and we have many happy customers using it. There are definitely challenges with that business, however, that made us look for easier ways to get people using the platform we had built. People looking to do ephemeral environments have a lift to move their environment definitions into Release and it's a work effort that needs prioritization. Release.ai is built on the same platform and because AI frameworks are more turn key than bespoke software stacks companies have been building on, we believe Release.ai will be easier to adopt. In the long run AI applications and traditional web applications are going to merge and we think we're the platform that will do that in the long run. Long story short, hundreds of iterations.
Thanks for the feedback and I agree we need to do a better job messaging the value on the site. How would this have landed for you?
We are an AI orchestration platform that makes deploying open source models and frameworks using Kubernetes and docker simple. We manage the GPU and k8s resources, provide templates to common open source frameworks and an orchestration engine for your AI workflows.
I think at the end of the day, I have a bunch of config files and commands. Showing a quick translation between the spaghetti and your solution would make the most sense. The less language I have to parse the better.
i.e. you have a set of kubernetes CRDs probably managed by a gitops solution -> we do this for you, you have a bunch of different pyproject.toml files that need to be orchestrated into a docker container -> this is what that looks like in release, tbh our terraform isn't a huge bottleneck because so much just ends up going in the kube crds.
maybe have two pitches: 1 for startups getting started and 1 for startups who already have a lot of this figured out (probably your bigger target audience if you have a strong pitch)
Yeah, I hear you and the confusion. We decided on this as a management fee that only gets charged when you’re using the environment. It was the best tradeoff we could come up with but it definitely isn’t perfect. Any ideas on how we can make this clearer or better?
It's funny you ask this because this question has come up a bunch of times. It just maps to our mission and we decided we really wanted to be true to it. Our mission is to help people/companies release their ideas to the world quickly. So it just fit and we decided it was worth the tradeoff for it to be a little harder to search for. In the end if we're successful it will be because we built something people want (i.e. apple.com) vs the name we chose.
