With Architect, any developer can create preview, staging, and even prod environments. And we're dependency-aware and powered by GitOps so that every PR spins up a deployment that is production-grade, including the APIs, databases, and events it needs to run.
I use nestjs. After a quick look at the product introduction, it is a great efficiency tool that not only simplifies local container deployment, but also makes online deployment flexible and diverse, which is worthy of praise. I will comment after using it, the first impression is good.
I don't know how I ever lived without Architect. I'm a 2X co-founding CTO so I'm always on the hunt for ways to speed up time-to-MVP. With Architect I've spent just a few hours on devops at my current startup. Total. It was dead simple to spin up my fully functioning app with a load balancer, app servers, job queue, cache, DB, CI/CD, etc. But the best part is I haven't lost flexibility to scale as needed. Oh, and I get a production-like dev environment, staging and even preview environments out of the box with no extra work.
If you're a developer with deep understanding of the tech, people, and processes of Ops, deployment may be just one more step in the dev chain. But for many humans that's not the case. If we're lucky we sometimes collaborate across teams to build and maintain effective CI/CD- and in a prefect world CD&D. But even then, dependency unknown unknowns can still push us into frantic troubleshooting or worse, weekend deployments. I love the idea of letting the platform solve the "It worked on my laptop" problem to let me focus on the creative work I enjoy.