Free Next.js SSR. No Bill Shock. Here’s How We Did Both.

Today we shipped two things that change the math for anyone hosting a Next.js app or a Node-backed side project. First, Katika Web Services now offers free-tier Next.js SSR — not just static export, but real server-rendered Next.js with the App Router. Second, we’ve built a structural promise into every paid plan: we pause sites when you hit monthly caps, instead of billing you for overage.

Both launches are aimed at the same audience: solo developers, freelancers, and small teams who want the deployment experience modern hosting offers, without the recurring fear of opening their inbox to a four-figure invoice.

Here’s what we shipped, why we built it this way, and where we’re deliberately drawing a line.

Free Next.js SSR, Including the Cold Start

Until today, every hosting provider that offered free Next.js SSR was a thin wrapper around Vercel or Cloudflare. KWS now serves Next.js SSR on its own infrastructure: per-project Node processes, automatic SSL on a <slug>.katikaws.com subdomain, and the same git-push-to-deploy flow we already had for static sites.

The trade-off, which we’re going to be plain about: free-tier SSR processes auto-suspend after 5 minutes of inactivity. The first request after a quiet period takes a few seconds while the process wakes back up. Every request after that is normal speed. This is the same model serverless platforms use behind the scenes — we’re just honest about it on the free tier instead of pretending it doesn’t exist.

If you don’t want cold starts, the Starter plan bumps the idle window to 30 minutes, and Pro and above are always-on with more memory and CPU. The deploy command is identical:

cd my-nextjs-app
npm install -g @katikaws/cli
kws deploy

That’s it. The platform detects Next.js, runs the build, allocates a port, spawns the process under pm2, and wires up the Apache reverse proxy. Within about 30 seconds you have a live URL.

No Bill Shock. Ever. As a Structural Promise.

You can scroll through Hacker News on any given week and find a horror story. A developer wakes up to a $1,100 bandwidth bill. A side project gets hit with a botnet and racks up a four-figure overage. A misconfigured cache amplifies traffic 200x and the invoice arrives before the team even notices the spike.

This isn’t a flaw in the platforms it happens on. It’s a deliberate billing model. Usage-based pricing means usage that doubles doubles your bill, and platforms count on most customers never hitting their hard caps even if those caps are technically available somewhere in the dashboard.

We took the opposite approach. Every plan on KWS — including the free tier — has explicit monthly caps on bandwidth, request count, build minutes, and SSR compute time. When you hit a cap, your affected site gets paused, not billed. Visitors see a calm "Site paused, will resume on the 1st" page until either the monthly counter resets or you upgrade your plan. We don’t charge you a penny of overage.

You get a heads-up email at 50%, 80%, and 95% of any cap, and a paused notice if you hit 100%. The emails all reinforce the same message: this is a courtesy, not an invoice.

What the Caps Actually Look Like

Here are the headline numbers per plan. Full breakdown is on the hosting plans page.

Plan	Bandwidth	SSR Compute	Idle Suspend	Price
Free	100 GB / month	16 hours / month	5 minutes	$0
Starter	500 GB / month	167 hours / month	30 minutes	$4.99 / month
Pro	1 TB / month	Always-on	Never	$20 / month
Business	5 TB / month	Always-on	Never	$99 / month

On every paid plan, if you ever do hit a cap, you can upgrade to the next tier from the dashboard and your site is back online in seconds. There’s no waiting room, no support ticket, no surprise charges. We’d rather you upgrade because you outgrew the plan than tolerate a stranger’s invoice.

What We’re Not Going to Copy

It would be dishonest to pretend KWS matches every Vercel feature. We’re smaller, single-region, and deliberately not chasing the edge-network arms race. A few things you’ll find on Vercel that we’re not building:

• Edge functions (V8 isolates). The infrastructure to run these in 30+ regions is an eight-figure investment we’re not making. If your application requires sub-50ms response times from any point on Earth, Vercel and Cloudflare are still the right answer.
• Built-in serverless databases. Vercel just deprecated their own (KV / Blob / Postgres) and moved customers to Neon and Upstash. We’re starting in the right place — we partner with database providers instead of trying to host them.
• Multi-region compute. KWS serves from a single datacenter. For most North American and European traffic, latency is fine. For a globally distributed audience, edge platforms still win.

What we offer instead is a flat-priced, predictable, single-region platform with a feature mix that works for 80% of projects. If you need the other 20%, you know who you are, and you should pay them.

Who This Is For

The clearest fit:

• Indie hackers shipping side projects. Vercel’s Hobby plan prohibits commercial use; ours allows it. If your side project starts making money, you don’t need to migrate the day you charge your first customer.
• Freelancers deploying client sites. One bill per month, one dashboard, no per-seat pricing. Domain, email, and hosting from one provider means one invoice to mark up.
• Small SaaS teams. Pro at $20 / month is comparable to Vercel Pro’s single seat — but with monthly caps and no per-team-member multiplier.
• Anyone who has ever opened a $1,000+ hosting bill they didn’t expect. The structural promise is the entire point.

How to Try It

Three steps from zero to a live Next.js SSR site on the free tier:

1. Sign up at katikaws.com and pick the Free tier.
2. Install the CLI: npm install -g @katikaws/cli and run kws login.
3. From your Next.js project directory, run kws deploy. The platform handles the rest.

Within about 30 seconds you have a live URL on a <slug>.katikaws.com subdomain. Connect a custom domain in the dashboard whenever you’re ready, or register a new one directly on KWS for a single-pane setup.

What’s Next

The roadmap from here is built around the same principle: predictable pricing as a feature, not a marketing line. We’re building scheduled cron jobs, a configurable firewall with bot-blocking and rate-limit rules, and DDoS bill-shield protection that auto-throttles malicious traffic before it touches your bandwidth meter. We’ll announce each one when it ships — not before.

If you’ve been waiting for a hosting platform that treats predictable bills as a structural feature instead of a "Pro tier" upsell, this is it. Try the free tier, ship something real, and let us know what you build.