Your code is your infrastructure.

Write your ExpressJS/NestJS app: routes, cron, queue. laranja reads it on your machine and turns each one into real resources in your own cloud. No upload, no copy, no console.

Get startednpx laranja deploy →
123456789
import express from "express";
import { http } from "@alzulejos/laranja-decorators";
import { listOrders, createOrder } from "./orders";

const app = express();
app.get("/orders", listOrders);
app.post("/orders", createOrder);

export default http(app);
● terminalbash▢ ✕
$ npx laranja deploy 🍊 laranja · reading ./src on this machine   🔑  account  123456789012 · eu-west-1  📦  build    2 routes · 1 cron · 1 queue → 4 λ  🌐  http     https://k3f.execute-api.eu-west-1…  ⏰  cron     refresh · every 5 min  📨  queue    receipts → SQS   ✨ live
bring your appexpressGCP soon
how it works

Real infrastructure — grown from your code.

1

Write ExpressJS/NestJS

Routes and decorators in plain TypeScript. No YAML, no separate infra repo to keep in sync.

2

Deploy locally

laranja reads your code on your machine and provisions it 1:1 into your own cloud account, using your own credentials.

3

Own it

Your code, your resources, your bill. Outgrow laranja? Eject to plain CDK and walk away — no lock-in.

roadmap

One command today. More clouds tomorrow.

Live today, with more on the way — the same code, provisioned in more places.

  1. ShippedHTTP appsExpress & NestJS routes, provisioned 1:1.
  2. ShippedJobs & queuesCrons and SQS workers, straight from decorators.
  3. ShippedWorkers & dashboardMulti-root workers and a live deploy dashboard.
  4. ShippedAzureThe same code on Azure cloud.
  5. BuildingHosted on laranjaNo cloud account? Deploy to ours, at you.laranja.io.
  6. PlannedAPI GatewayA first-class HTTP API front door.
  7. PlannedGCP & CloudflareMulti-cloud, still one command.

Missing a provider or framework? The roadmap bends to what people actually deploy — tell us what you need →

your code stays yours

We never get a copy of your code.

🔒

Read on your machine

The scan runs entirely in your CLI. Your source, secrets and env vars are never uploaded — there's nothing for us to leak.

✂️

Stripped before sync

Only a stripped manifest of what you deployed — resource names and counts — is synced to your dashboard. No code, ever.

🔑

Straight to your account

Deploys go directly from your machine to your cloud with your own credentials. laranja is never in the path of your data.

how it compares

The your-cloud path, without the trade-offs.

Everyone else makes you pick one: someone else's cloud, one framework, or a DevOps degree. laranja doesn't.

laranjaMauSSTEncoreRailway · Render
Runs in your own cloud account✓✓✓✓—
Any Node framework✓NestJS only✓Encore only✓
No keys or repo to hand over✓—✓——
Zero extra IaC to write✓✓CDK✓✓
Eject to plain IaC you own✓—✓——

The line that matters: laranja asks for nothing — no IAM user to create, no repo to connect. It runs on your machine with the credentials already there, writes no extra IaC, and ejects to plain CDK the day you outgrow it. laranja vs Mau in detail →

pricing

You pay to deploy. Your cloud does the rest.

Start free, no card. Every tier deploys into your own cloud, so the only bill that scales is your provider's — not ours.

Loading plans…