Write a plain Node.js app with expressJS/NestJS — routes, cron, queue — and laranja provisions it 1:1 into your own cloud with one command. No YAML, no keys to hand over, no lock-in.
No reviews yetBe the first to leave a review for laranja
Maker
📌
I kept watching backend devs — myself included — lose whole days to infrastructure just to get a NestJS app onto the Cloud. You either hand-write mountains of CDK/Terraform, or you reach for a platform that asks for a long-lived, near-admin IAM key and quietly runs everything on its own servers. Neither felt right: one is toil, the other is a trust and lock-in problem. So I set out to build a deploy tool that reads your code — your routes, crons, and queues are already declared there — and turns that into real AWS/Azure/GCP infrastructure, with no IaC to write and no standing credentials to hand over.
The approach shifted a lot along the way. I started by generating infrastructure locally on the developer's machine, but that meant shipping a heavy synth engine into every install and made the logic hard to evolve. The turning point was splitting the work: the CLI builds your app and produces a small intermediate representation, the server synthesizes the CloudFormation from that, and your own machine executes the deploy with your own credentials. That one decision is what makes laranja both zero-config and something you never have to trust with the keys to your account — and if you ever outgrow it, you can eject to plain IaC and walk away.
Report
Finally something that lives up to the "one command" promise, I pointed it at a small Express app with a cron job and it spun up the same stack on my AWS without me touching a single YAML file. The lack of vendor lock-in is what got me to actually try it.
Report
Maker
@aozkol89727 Thanks for checking it out! 🙌 I'd love to hear your feedback and learn if there's anything we can add to make your workflow easier.
Report
Tried it on a small nestjs project with a cron job and redis queue. The one command actually pushed a working setup to my cloud account without me touching any YAML, which honestly surprised me for something this simple.
Report
Maker
@aksaytahir43218 Thanks for checking it out! 🙌 We're still early, and every bit of feedback helps us improve. I'd love to hear your thoughts and what features would make your experience even better.
Report
Maker
Starting from V0.6.0, http://laranja.io now supports deploying ExpressJS/NestJS apps on AWS/Azure
Report
Finally something that actually deploys my express app without me writing 200 lines of YAML or hunting down a dozen IAM keys. The one-command provisioning into my own cloud felt almost too smooth.
Report
Maker
@nurullahgngf Thanks for checking it out! 🙌 We're still early, and every bit of feedback helps us improve. I'd love to hear your thoughts and what features would make your experience even better.
Finally something that lives up to the "one command" promise, I pointed it at a small Express app with a cron job and it spun up the same stack on my AWS without me touching a single YAML file. The lack of vendor lock-in is what got me to actually try it.
@aozkol89727 Thanks for checking it out! 🙌 I'd love to hear your feedback and learn if there's anything we can add to make your workflow easier.
Tried it on a small nestjs project with a cron job and redis queue. The one command actually pushed a working setup to my cloud account without me touching any YAML, which honestly surprised me for something this simple.
@aksaytahir43218 Thanks for checking it out! 🙌 We're still early, and every bit of feedback helps us improve. I'd love to hear your thoughts and what features would make your experience even better.
Starting from V0.6.0, http://laranja.io now supports deploying ExpressJS/NestJS apps on AWS/Azure
Finally something that actually deploys my express app without me writing 200 lines of YAML or hunting down a dozen IAM keys. The one-command provisioning into my own cloud felt almost too smooth.
@nurullahgngf Thanks for checking it out! 🙌 We're still early, and every bit of feedback helps us improve. I'd love to hear your thoughts and what features would make your experience even better.