381 karma · joined May 29, 2019
From a value perspective, we have a simple per-seat pricing.
There is no easy answer but here is my response: 1. We take precautions to enable connections through oauth/app mechanisms for VCS integrations and IAM roles for cloud accounts like aws and gcp 2. Our incentives are aligned - we make money only if we earn and keep the trust of our customers 3. We have gone to extra lengths to enable easy exits in case companies want to move out.
These, broadly speaking, are true for any other provider that you would use and may now trust for app hosting or CDNs or version control or payments - some of which are SmallCos and some were SmallCos until just a couple of years ago.
At some level, it all boils down to "trust us" but hope this provides context.
However, in the Argonaut context, that only limits the overall infra management piece where we don't have a seamless integration using IAM roles and can't provision infra like dbs and queues. The app deployments to Azure kubernetes (or any k8s cluster) work seamlessly though, and some of our customers deploy to AKS in this manner.
There is a little "bulb" icon on the top. That enables a "highlight mode" where you can select some text, usually kubernetes error messages. That is sent to an OpenAI LLM to (1) convert the error into plain english (2) show potential fixes.
This is limited by what GPT4 can provide but it is still helpful in some cases. Maybe we should highlight this feature more :)
> Kubernetes feels like a leaky thing to throw abstractions over, so the pain with using it is you need to become an expert in it, [..]
We believe two things: (1) k8s features exist because they are genuine user needs and we don't want to hide them (2) things get very complex very quickly because the "beast" is complex.
Argonaut's approach is what I call "Progressive Discovery". There is a good happy path that works for 80% of use cases. When you need to deviate, we make it easy to work with the underlying primitives to enable your use case. This enables users to move fast without hitting an abstraction ceiling and it keeps the complexity in check.
That said - Argonaut is not for everyone. If you have just a service or two, you're better off running it on a hosted runner instead of an aws or gcp or azure. It is going to be cheaper at small scale too.
I assume you are already containerized, so there is not much to be done. There is a one time setup of a kubernetes cluster (EKS) that aws takes about 25mins for.
This will give you a rolling zero down-time deploy out of the box along with a few other goodies. You can checkout a quick demo here (~4m) - https://www.youtube.com/watch?v=8DZsYXxA2tQ
We're building a similar service with the aim of being a comprehensive platform across managing cloud infra across stable envs like staging and prod (rds, s3, elasticache, opensearch etc. on aws and cloudsql, gcs, gke, memorystore on GCP) and app deployments onto kubernetes on those environments.
Some things we have heard from talking to customers are that they prefer a single tool to manage their cloud infra, setting up (stable) environments, CI/CD (push to deploy from github/gitlab), kubernetes runtime (EKS, GKE) and app deployments.
I understand that kubernetes is a divisive topic on HN because kubernetes is overkill for a lot of companies and can become complex. That said, there are companies which have a genuine need for something like kubernetes and find working with aws/gcp a chore. We might be restricting our market but adding value to such teams is what we are betting on at the moment.
What would be the most valuable to you if you are in the market for a tool such as Argonaut? I'd love to shape our product to be genuinely useful for folks here.
That's the model we use at argonaut.dev. We charge a flat fee per developer and you pay the AWS bills to AWS or GCP (using credits ideally). We settled on this because it is transparent and does not lead to any surprises in billing, especially for startups which are our core target.
We have customers who have evaluated and chosen us for our flexible CI/CD pipelines, transparency, and pricing. We also help setup other infra dependencies you might have like managed databases, redis on aws and gcp.
Also, you missed out my company, argonaut.dev :-)
Argonaut (https://www.argonaut.dev) provides a fully managed, production-ready internal developer platform for software engineering at scale. We automate deployments of infrastructure and applications to your cloud account and integrate with GitHub, GitLab, AWS, and GCP. Our mission is to revolutionize the way software is developed, making it faster, more efficient, and seamless for engineering teams worldwide.
If you're passionate about developer tools, cloud computing, and streamlining software development, I'd love to hear from you. Here's more about the role and the interview process - https://www.ycombinator.com/companies/argonaut/jobs/pJavmIJ-...
Here's how to use it - https://www.loom.com/share/d0f8cd515ceb441f8d0c13e45d9f6992
It is meant for simple automation - please use it responsibly!
There are a few solutions that exist already, with a similar objective. Okteto and Portainer are OSS comparables. There are a few closed source ones as well.
This space is still fairly nascent though and it's always nice to see more people resonating with the need for this. Note: I have a horse (argonaut.dev) in this race.
Disclaimer: I'm the founder
It's either very smart (if they pull it off) because they will have a ginormous cost advantage or they fail.
I'm personally of the opinion that the ux on top of aws/gcp/... is worse than a doo-doo in a shoe. However, they are as stable as can be (all complex systems go down once in a while). There are very few mature projects that do not rely on aws/gcp/... managed services anyway. Might as well put in the little bit of effort to set yourself up for the future instead of painful migrations. This obviously doesn't hold for hobby projects.
In any case, I have a lot of respect for the engineering that fly does. Kudos.
It's an amazing project by a solo dev, please consider sponsoring. My guess is anyone using kubernetes can afford to get their org to shell out $10 for it.
(I'm not affiliated with k9s in any way except as a happy user)