These look all the same. I honestly don't know how people choose one over the other. It's like roulette, gotta pick a random one.
It is interesting that YC has invested in many of these similar PaaS already and they keep doing it. Some names that I have come across (all are YC backed): - Nullstone - Aptible - Porter - Flight Control - Fly.io I have a feeling I am missing more.
Can't blame them really, wrapping a few AWS calls in $lang and pitching it to VC as a "disruptor" is a decent techbro playbook. Don't hate the player, etc.
It is interesting that YC has invested in many of these similar PaaS already and they keep doing it. Some names that I have come across (all are YC backed): - Nullstone - Aptible - Porter - Flight Control - Fly.io I have a feeling I am missing more.
Do they all use the same IaC (guessing Terraform..) under the hood?
As other replies have mentioned, Terraform is challenging to create a smooth experience. We have spent many cycles working on smooth orchestration so that it's fast and intuitive. Our primary motivation was to avoid hiding infrastructure behind proprietary technology.
We have support for other IaC tools on our roadmap so that each team can use what is comfortable.
AWS Copilot has been great for deploying `services`. But I wasn't sure if the `jobs` were what I was looking for, since they are event triggered. I'll test it our now. Essentially I'd like to build a docker image of code from a repository, and deploy and run it, and manage its lifecycle. Perhaps I could copy the CF template from the Copilot to do the same.
> Essentially I'd like to build a docker image of code from a repository, and deploy and run it Presumably, you're running it based on some input. Jobs are the right paradigm if this input is periodic (for example, processing a batch of items in S3 every few hours). Otherwise, you may want to consider a Worker: https://aws.github.io/copilot-cli/docs/concepts/services/#wo... which can be connected to an SQS queue and…
(I'm the cofounder of Coherence) I consider the "best-in-breed" tools with this shape to break into the following categories: "Infra Abstractions": DuploCloud, Massdriver, Stacktape "PaaS in your own cloud": Nullstone, Zeet, Quovery, Porter, Architect.io, FlightControl "SDLC Platform for Teams": Coherence (withcoherence.com) - the key difference here is in how CI/CD (incl integration tests) are handled, how developme…
We are from DuploCloud and hence the following note might be biased. The downside of a pure paas solution like porter, Quovery at al. is that they have a limited scope say kubernetes, pieplines and diagnostics. All of the lower layers of the Devops stack from IAM, networking, AWS services (including non containerized workloads like Lambda, EMR, Airflow etc), scores of compliance and security controls are left out of scope. Then one needs a expert Devops to write boat loads of TF. Our apporoch is of a E2E platform that should do all of what a human devops manually scripts. Thus fundamentally deliver self-service, labor reduction and compliance.
These look all the same. I honestly don't know how people choose one over the other. It's like roulette, gotta pick a random one.
Which ones deploy to your own cloud accounts?
I built yet another similar platform with the goal to keep accounts fully isolated, while it started with preview environments only, we started handling some prod deployments too.
There are nice perks on this approach but the complexity (for us) is non-negligible.
We considered Discord, but went with Slack (mainly because we have dedicated support channels for customers). If we provided a Discord, would that be more appealing to join?
For me yes. A lot of my professional communities use Discord. It seems like a pretty even split so I find myself using both and preferring Discord.
Kubernetes is kind of the intellectually honest, logical end point of this stuff.
That's like saying hammers are a logical end point of trying to get carpentry work done. Kubernetes is an incredibly useful tool, but it needs at least one layer of abstraction (possibly multiple) on top of it to make it useful for the typical company that isn't doing anything out of the ordinary.
I think of kube as the new de-facto OS, just like Linux back then. Of course it needs config to make it useful for your needs but I think it's really the platform to target for the next decade at least.
Is there ever going to be another Dropbox? B2C for developers is really something. Some junior in some huge org, is he going to put his AWS security credentials into a box and expense the $100 a month? Maybe. It seems really against trend. You're making something for ultra-junior developers who are going to be asking ChatGPT (or whatever soon-to-be vendor LLM) for a solution, which can't interact with UIs. And how is…
I think you give ChatGPT too much credit. Sure, it'll give you a great algorithm in general languages, but in my experience it's still really bad with IaC for anything non-trivial.
$100/user/mo seems like way too much. The “contributing code that is deployed through Nullstone”. Makes it sound like you have to pay for the whole engineering team even if only a few devs are actually handling the deployments. Is that true?
Thanks for the feedback! I do think that AI is going to have a massive impact on development including cloud infrastructure; however, we rarely see junior developers setting up cloud infrastructure because it is dangerous. Our motivation is to make the cloud easier for all skill levels. In many organizations, this usually requires platform engineers or lead engineers that determine what works best with their technica…
> we rarely see junior developers setting up cloud infrastructure because it is dangerous. So whom is this for? Doesn’t this set up cloud infrastructure? Dangerous how exactly? It’s not a tautology. Someone who can’t handle like, using AWS directly, is a junior developer. Another perspective is the founderese is not very reassuring.
More senior folks can be specialized in other things, and be less than great at infrastructure code. I think I can hold my own when it comes to Terraform, but that doesn't mean I don't have to fight with IAM for longer than I care for, on the regular.