# Light Cloud Blog

> Writing from the Light Cloud team on deployment, cloud infrastructure, and the platform.

## Posts
- [Where to Host a SaaS App](https://blog.light-cloud.com/comparisons/where-to-host-a-saas): Where to host a SaaS app before it has paying customers: frontend, API, Postgres and your own domain priced on 8 platforms, from $5 a month to about $40.
- [Trust Math, Not Vendors](https://blog.light-cloud.com/sovereignty/trust-math-not-vendors): Confidential computing lets a CPU run your workload inside a box its own operator can't open, and prove it. That ends a real class of trust problems. The legal problem walks around the cryptography and meets you at the endpoints.
- [Spring Boot on Light Cloud: JAR, Port and Memory Settings](https://blog.light-cloud.com/tutorials/deploy-a-spring-boot-app): Deploy a Spring Boot app to Light Cloud without a Dockerfile: Gradle or Maven builds the JAR, SERVER_PORT is set for you, and JAVA_TOOL_OPTIONS=-XX:MaxRAMPercentage=75 raises the heap from 123 MB to 371 MB on a 512 MB instance.
- [A Go (Gin) API Deployed in Five Steps](https://blog.light-cloud.com/tutorials/deploy-a-go-api): Deploy a Go API built with Gin to Light Cloud without a Dockerfile: go.mod and main.go at the root, PORT from the environment, GIN_MODE=release, JSON logs with a severity, and a quarter-second cold start.
- [AI Writes Your Terraform. That's the Problem.](https://blog.light-cloud.com/ai-infra/ai-writes-your-terraform): 84% of developers use AI tools; 46% distrust their accuracy; 3% highly trust them. Now the industry is aiming that tool at infrastructure, where the test suite is production. The fix is a deterministic model, not a smarter autocomplete.
- [Deploy a NestJS API with a Database Connection](https://blog.light-cloud.com/tutorials/deploy-a-nestjs-api): Deploy a NestJS API with PostgreSQL on Light Cloud: PORT from the environment, a pg pool sized for serverless, request validation, a health check that tests the database, and why the start script should run node dist/main.
- [A Flask App in Production, Without Writing a Dockerfile](https://blog.light-cloud.com/tutorials/deploy-a-flask-app): Deploy a Flask app to Light Cloud without a Dockerfile: app.py, templates and static files, gunicorn started for you on the right port, the Python version from .python-version, and settings from environment variables.
- [The Pendulum Swings Local](https://blog.light-cloud.com/dev-tools/the-pendulum-swings-local): The laptop on your desk embarrasses the VM you rent, WASM made compute portable, and local-first made state survivable offline. The pendulum is swinging. The skill is predicting which workloads it takes with it.
- [Environment Variables and Secrets: Build Time vs Run Time](https://blog.light-cloud.com/tutorials/environment-variables-and-secrets): How environment variables work on Light Cloud: static sites read VITE_ variables at build time and bake them into public JavaScript, containers read variables at run time. Where secrets are safe, verified on a live site.
- [Django + PostgreSQL on Light Cloud: Migrations, Static Files and a Live Admin](https://blog.light-cloud.com/tutorials/deploy-django-with-postgres): Deploy Django 6 with PostgreSQL on Light Cloud without a Dockerfile: settings from environment variables, migrations from your laptop, static files with WhiteNoise, and a working admin behind HTTPS.
- [Serverless Was a Pricing Model, Not an Architecture](https://blog.light-cloud.com/cloud/serverless-was-a-pricing-model): Lambda's real invention was billing that hit zero when idle. Everything else, the cold starts, the timeouts, the event-glue architectures, was the price of getting that bill, and a decade of system design contorted itself around a meter.
- [A Preview URL for Every Branch, Posted on Your Pull Request](https://blog.light-cloud.com/tutorials/preview-url-for-every-branch): Get a preview deployment for every Git branch on Light Cloud: each pull request gets a live URL in a bot comment and a GitHub check, and the preview is deleted when the branch is. No CI config to write.
- [Put a Password on a Staging Site Before the Client Sees It](https://blog.light-cloud.com/tutorials/password-protect-a-staging-site): Password-protect a staging site on Light Cloud: a branch gets its own environment and URL, a password in the Security tab locks it at the edge, and production stays public. No code, no .htaccess, no auth middleware.
- [FastAPI in Production: From main.py to a Public URL](https://blog.light-cloud.com/tutorials/deploy-a-fastapi-app): Deploy a FastAPI app to Light Cloud without a Dockerfile: requirements.txt and main.py are enough, uvicorn is started on the right port, and the Swagger docs at /docs are live in about 90 seconds.
- [Kubernetes Won. Developers Lost.](https://blog.light-cloud.com/kubernetes/kubernetes-won-developers-lost): Kubernetes hit 82% production adoption and got crowned the operating system for AI. Total victory. And the losers are application developers, who were never supposed to touch a kernel, and now write YAML against one for a living.
- [Put a Node.js Express API Online: Port, Environment Variables and Logs](https://blog.light-cloud.com/tutorials/deploy-an-express-api): Deploy an Express 5 API on Light Cloud without a Dockerfile: listen on PORT, read settings from environment variables, write JSON logs with a severity, and find every request in the Logs tab.
- [Deploy a SvelteKit Site as Static Files: adapter-static and Prerendering](https://blog.light-cloud.com/tutorials/deploy-a-sveltekit-app): Deploy a SvelteKit site with adapter-static to Light Cloud: fix the Encountered dynamic routes error with export const prerender = true, and get real HTML pages served from the edge, deep links included.
- [Regulators vs. the Duopoly](https://blog.light-cloud.com/industry/regulators-vs-the-duopoly): The UK spent three years investigating cloud competition, recommended designating AWS and Microsoft as strategic-market-status suppliers, and then accepted voluntary commitments instead. A field guide to telling real remedies from theater.
- [How to Deploy an Angular App on Light Cloud, Deep Links Included](https://blog.light-cloud.com/tutorials/deploy-an-angular-app): Deploy an Angular 22 app made with the Angular CLI to Light Cloud: the dist/<project>/browser output folder is detected automatically, Angular Router deep links work, and every git push redeploys.
- [How to Deploy a Vue 3 App with Vue Router and TypeScript on Light Cloud](https://blog.light-cloud.com/tutorials/deploy-a-vue-app): Deploy a Vue 3 app made with create-vue, including Vue Router history mode and TypeScript, to Light Cloud: detected automatically and live in about 30 seconds.
- [Deploy a React App in Minutes: Your First Light Cloud Website, for Free](https://blog.light-cloud.com/tutorials/deploy-a-react-app): Create a React app with Vite, push it to GitHub and deploy it on Light Cloud's free plan: detected automatically, built in 15 seconds, updated on every git push.
- [What "Open" Means After HashiCorp](https://blog.light-cloud.com/devops/what-open-means-after-hashicorp): Terraform went BSL in 2023, the community forked it, and IBM bought the company anyway. The lesson isn't that HashiCorp was villainous. It's that a license is a contract one side can rewrite, and your infrastructure planning has to price that.
- [Microservices Part 6: Trace One Request Through the Logs](https://blog.light-cloud.com/tutorials/microservices-on-light-cloud-part-6-logs-and-tracing): Trace a request through two Light Cloud services with a shared x-request-id, write JSON logs with a severity field, and use the Logs tab's search and level filter to find failures fast.
- [Microservices Part 5: Preview a Branch and Roll Back](https://blog.light-cloud.com/tutorials/microservices-on-light-cloud-part-5-branches-and-rollback): Use Light Cloud branch environments to preview a change across three services, merge it into production, and roll back a bad deploy in 13 seconds without a rebuild.
- [The VMware Lesson](https://blog.light-cloud.com/industry/the-vmware-lesson): AT&T told a court it was facing a 1,050% price increase. CISPE members reported hikes up to 1,500%. Broadcom's VMware playbook wasn't a scandal; it was a valuation of switching costs, executed precisely, and it predicts the next consolidation wave.
- [Microservices Part 4: Cold Starts vs Always On](https://blog.light-cloud.com/tutorials/microservices-on-light-cloud-part-4-cold-starts): Measure cold starts on Light Cloud with curl, compare scale to zero with an always-on instance, and use real numbers to set timeouts and decide what to keep warm.
- [Microservices Part 3: Autoscale Under Load](https://blog.light-cloud.com/tutorials/microservices-on-light-cloud-part-3-autoscaling): Load test a Light Cloud service with oha, watch it scale from zero to five instances, and learn why concurrency and database connection pools decide how well autoscaling works.
- [The Capex Arms Race Orphans Small Workloads](https://blog.light-cloud.com/industry/capex-arms-race-orphans-small-workloads): Hyperscaler capital is stampeding toward AI factories, and the ordinary developer workload, a container, a database, a preview environment, is nobody's priority. That neglect is the opening every developer cloud is built on.
- [Microservices Part 2: Connect Your Services Safely](https://blog.light-cloud.com/tutorials/microservices-on-light-cloud-part-2-connect-services): Allow several browser origins with CORS, rotate the secret your services share without dropping a request, and add a timeout between services, step by step on Light Cloud.
- [Microservices Part 1: Deploy a Frontend, Two APIs and a Database](https://blog.light-cloud.com/tutorials/microservices-on-light-cloud-part-1-deploy): Deploy a React frontend, a Node.js API, a Python FastAPI API and PostgreSQL from one GitHub monorepo on Light Cloud, step by step, with every screen shown.
- [Power Is the New Region](https://blog.light-cloud.com/industry/power-is-the-new-region): Three Mile Island is being restarted for a single customer. Hyperscalers are buying reactors because the constraint on cloud capacity stopped being racks or chips and became megawatts, and that breaks a decade of assumptions about regions.
- [Neoclouds and the Great Unbundling](https://blog.light-cloud.com/industry/neoclouds-and-the-great-unbundling): CoreWeave went from crypto-mining afterthought to a public company with a $99 billion backlog by selling exactly one thing well. The specific companies may wobble. The procurement habit they taught buyers won't.
- [The Honest Math of Cloud Repatriation](https://blog.light-cloud.com/cloud/the-honest-math-of-repatriation): The loudest cloud exit in the industry ended quietly in the summer of 2025 when 37signals' last petabyte left S3. Their published numbers are real. So are the reasons most companies copying them would lose money.
- [Three Companies in a Trench Coat](https://blog.light-cloud.com/industry/three-companies-in-a-trench-coat): On the morning of November 18, 2025, EU regulators published their list of critical cloud providers. That afternoon, Cloudflare fell over and demonstrated it. The autumn outage cluster wasn't three stories. It was one.
- [Light Cloud + Claude Code: Deploy Your App with AI](https://blog.light-cloud.com/ai-infra/one-command-claude-code-light-cloud): Install the Light Cloud MCP server in Claude Code with one command, ask it to deploy a folder, and get a live URL. A real session with screenshots: deploy, redeploy, password.
- [Egress Fees Are Dead. Lock-In Isn't.](https://blog.light-cloud.com/multi-cloud/egress-fees-are-dead-lock-in-isnt): Exit egress fees died in 2024 and the EU Data Act finishes the job in January 2027. Celebrate briefly. The billing lock died precisely because it was the lock that mattered least, and the four that matter are doing fine.
- [Your Regulator Now Requires an Exit Plan](https://blog.light-cloud.com/sovereignty/your-regulator-wants-an-exit-plan): Since January 2025, EU financial entities must hold documented exit strategies for critical ICT providers, and since November 2025 the providers themselves are under direct supervision. The plan is now a compliance artifact. A real one is still rare.
- [Next Round I'm Bringing My Own Knives. Watch Me Cook.](https://blog.light-cloud.com/startup/pitching-at-accelerator): Three minutes, no laptop, and a long drive still in my legs. I pitched the platform at KitchenPitch, FreshMango's pitch day, and left out the best thing we are building. Here is why that was the right call, what the mentors fixed afterwards, and the part where I did not recognize the accelerator CEO.
- [Why Europe Keeps Failing to Build Its Own Cloud](https://blog.light-cloud.com/sovereignty/why-europe-cant-build-its-own-cloud): GAIA-X, EuroStack, and now a 180-million-euro sovereign tender with Google inside the tent. Europe keeps trying to build a thing when what it lacks is a property, and the property is portability.
- [CADA: Europe Just Wrote a Tier List for Clouds](https://blog.light-cloud.com/sovereignty/cada-and-the-four-tier-future): The proposed Cloud and AI Development Act sorts cloud providers into four sovereignty levels. Tier lists reshape markets faster than mandates do, and startups selling into the EU public sector should read this one now, not at adoption.
- [The Most Honest Thing a Hyperscaler Ever Said](https://blog.light-cloud.com/sovereignty/the-most-honest-thing-a-hyperscaler-said): In June 2025, Microsoft France's legal director was asked under oath whether he could guarantee French data would never be handed to US authorities. He said no. It wasn't a scandal. It was a clarification, and Brussels heard it.
- [AWS European Sovereign Cloud, Six Months In](https://blog.light-cloud.com/sovereignty/aws-sovereign-cloud-six-months-in): AWS built a physically separate cloud in Brandenburg with its own IAM, billing, and EU-only operators. It's the most serious sovereignty engineering a hyperscaler has shipped, and the question that matters about it is legal, not technical.
- [Same App, Four Platforms: We Did the Math, and It's Not Close](https://blog.light-cloud.com/cloud/same-app-four-platforms): One reference app, four platforms, list prices only. Around $5 a month on Light Cloud, ~$14 on Render, ~$40 on AWS, and the gap widens the moment you add a staging environment. We show the arithmetic, and where the others still have an edge.
- [Sovereignty Is Not a Region Dropdown](https://blog.light-cloud.com/sovereignty/sovereignty-is-not-a-region-dropdown): Deploying to eu-central-1 makes you compliant with almost nothing. Jurisdiction follows the company that controls your data, not the building that houses it, and a growing amount of sovereignty marketing depends on you confusing the two.
- [The Metrics We Actually Track at Pre-Seed](https://blog.light-cloud.com/startup/pre-seed-metrics-that-matter): Every pre-seed deck leads with a growth chart, and most of those charts are statistical noise. Here are the numbers we actually watch: time-to-first-deploy, activation, and gross margin per workload type, and why.
- [Security When You're a Two-Person Infrastructure Company](https://blog.light-cloud.com/startup/security-as-a-two-person-company): Can a two-person company be trusted with your production workloads? That question deserves specific answers instead of vibes. Here's our threat model, what's done, and what honestly isn't.
- [Why We're Building a Desktop App in 2026](https://blog.light-cloud.com/dev-tools/why-a-desktop-app-in-2026): The decade that moved email, docs, design, and project management into the browser left the tools developers live in untouched. Every major development environment is a desktop app. ICE is one on purpose.
- [Why Our Source of Truth Is a Graph, Not a Text File](https://blog.light-cloud.com/devops/graph-not-text-file): Facebook figured this out in 2015: config errors were a major source of outages, and their answer was to compile configuration from source and model its dependencies. A decade later, most of us still review the characters instead of the structure.
- [Anatomy of a 3-Cent Preview Environment](https://blog.light-cloud.com/dev-tools/anatomy-of-a-3-cent-preview-environment): A full, disposable copy of your app for every branch sounds expensive until you see the meter. Here's the arithmetic that gets a preview environment to about three cents, and the engineering that keeps it there.
- [Every Company Is Building the Same Internal Platform, Badly](https://blog.light-cloud.com/industry/everyone-builds-the-same-platform-badly): Gartner said 80% of large engineering orgs would have platform teams by 2026. They do. And nearly all of them are assembling the same portal from the same parts, with no customers who can say no.
- [Multi-Cloud Is Overrated. Portability Isn't.](https://blog.light-cloud.com/multi-cloud/multi-cloud-overrated-portability-isnt): Three outages inside a month did not prove you need to run production on two clouds. They proved you need a credible, tested ability to leave one. Those are different products with wildly different prices.
- [Cloud Pricing Complexity Is a Business Model, Not an Accident](https://blog.light-cloud.com/industry/cloud-pricing-is-a-business-model): Egress fees survived for over a decade and died within nine weeks of EU regulation taking hold. Prices that behave like that aren't cost recovery. Cloud pricing complexity is a business model, and it's working.
- [Infrastructure Is Waiting for Its IDE Moment](https://blog.light-cloud.com/cloud/infrastructure-ide-moment): Code went from punch cards to editors to integrated environments. Infrastructure is still handing decks to the batch operator and waiting for the printout. The IDE moment hasn't happened yet, and text files won't be the thing that delivers it.
- [Cloud Pricing That Actually Makes Sense](https://blog.light-cloud.com/cloud/cloud-pricing-that-makes-sense): We built Light Cloud with transparent, usage-based pricing. No hidden fees, no complex calculators, no surprise bills. Here's how our pricing works and why it saves you money.
- [Deploy Full-Stack Apps in Minutes](https://blog.light-cloud.com/dev-tools/introducing-light-cloud): Light Cloud is a deployment platform that brings the simplicity of Vercel to full-stack applications. Deploy React apps, containerized backends, and PostgreSQL databases with a single click. No DevOps required.
- [Cloud CPR: A 5-Step Resuscitation Program](https://blog.light-cloud.com/startup/light-cloud-roadmap): People keep asking about our roadmap. Investors want timelines. Beta users want features. My therapist wants to know why I twitch every time someone says 'scope creep.' So here it is-five steps from scrappy MVP to enterprise cloud domination, complete with the delusion, optimism, and questionable life choices that got us here.
- [Light Cloud Joins Google Cloud for Startups Program](https://blog.light-cloud.com/startup/light-cloud-joins-google-for-startps-program): We got accepted into Google Cloud for Startups. Yes, we're building a tool to help you escape vendor lock-in, and yes, Google is giving us credits. The irony isn't lost on us.
- [AWS Goes Dark: How October 20's Outage Proved Multi-Cloud Isn't Just Paranoia](https://blog.light-cloud.com/multi-cloud/aws-goes-dark-october-20-2025): AWS had another 'minor hiccup' that only lasted 15 hours and affected over 1,000 companies. Here's why putting all your eggs in one cloud basket is like trusting a single parachute made of spaghetti.
- [Integrated Cloud Environment](https://blog.light-cloud.com/dev-tools/integrated-cloud-environment): Your enterprise-grade infrastructure in minutes, not months.
- [The Day I Explained Kubernetes to My Mom](https://blog.light-cloud.com/kubernetes/the-day-i-explained-kubernetes-to-my-mom): My mom asked what I do for work. Three hours later, she had accidentally designed a better container orchestration system using kitchen analogies. Here's what happened.
- [A Breakup Letter to YAML](https://blog.light-cloud.com/devops/yaml-breakup): After 47 indentation errors, 23 deployment failures, and one nervous breakdown, it's time we talked about our relationship, YAML.
- [The Arrival of the AWS Bill. Oil on canvas.](https://blog.light-cloud.com/startup/cloud-bill-horror-story): I went to sleep that night feeling like I'd conquered the cloud. Look at me, I thought, debugging infrastructure that AWS architects couldn't fix. I'm basically a DevOps deity now. Oh, sweet summer child.
- [So I Started a Cloud Company Out of Spite](https://blog.light-cloud.com/startup/cloud-out-of-spite): After spending the GDP of a small nation on AWS and losing what remained of my sanity to YAML files, I did what any reasonable developer would do: I started a company to fix it.
- [Why I Sacrificed a Goat to AWS gods](https://blog.light-cloud.com/cloud/rethinking-infrastructure): When I need to deploy a Node.js API with a Postgres database, I shouldn't need to understand VPCs, subnets, security groups, IAM roles, RDS parameter groups, and 47 other concepts.