Static.app

Operator's take

A lot of "just get it online" moments get stuck waiting for a developer to configure a server, mess with DNS, or set up a deployment pipeline that's overkill for a five-page marketing site. Static.app is built for exactly that gap: you drag a folder of files onto the page, and within seconds you have a live URL, HTTPS, and the option to connect your own domain. No terminal, no Git, no Netlify account you'll forget the password to in six months.

The use case it nails is narrow but common — portfolio sites, landing pages, event microsites, documentation, any HTML/CSS/JS work that doesn't need a database or server-side logic. Freelancers who hand off pre-built sites to clients, marketing teams who need a campaign page up before IT responds to the ticket, designers who want a real URL to share instead of a Figma link — this is the tool. A built-in code editor means you can make last-minute tweaks without reopening your local editor.

Where it stops: static only, full stop. No user logins, no dynamic content that requires a database. The free tier gives you one site and 50MB of storage, which is plenty for a portfolio or a simple landing page, but the hard ceiling is real. Forms are handled natively — add a static-form attribute to any HTML form and Static collects submissions for you, no third-party service needed. If you already know your way around Netlify or Vercel, you're not the audience here — those tools give you more power in exchange for more setup. Static.app is for the operator who wants the site live before lunch and has no interest in continuous deployment pipelines. Paid plans (Starter $5/mo, Medium $10/mo, Large $15/mo) layer in custom domains, workspaces, forms, analytics, and an API/MCP for connecting AI agents and automated deploy pipelines; GitHub Actions integration covers deploy-on-push. Team seats only appear at Medium (1 seat) and Large (3 seats), with extra seats at $5/mo each.

What it's good at

• One-click publish — drag a folder, get a live URL; no CLI, no server config, no deployment credentials to manage.
• Automatic SSL — HTTPS is provisioned and renewed automatically with no action required; the site is secure out of the box.
• Free subdomain on all plans — every account gets a free .static.domains subdomain; custom domain connection available on paid plans.
• Built-in code editor — make small copy or style changes directly in the platform browser without switching back to a local tool.
• Unlimited traffic on paid plans — every paid tier (Starter, Medium, Large) ships with unlimited bandwidth, so traffic spikes don't trigger overages; the site doesn't bill itself as edge-CDN specifically, but serving and SSL are handled for you.

What it's not

• Not a fit for dynamic apps — no server-side logic, no database, no user auth; anything beyond HTML/CSS/JS lives in a different category of tool entirely.
• Team features sit on the higher tiers — workspaces start at Starter ($5/mo), but team seats only appear at Medium ($10/mo, 1 seat) and Large ($15/mo, 3 seats); extra seats run $5/mo each (marginal — bulk buys discount slightly). The free and Starter tiers are effectively single-user.
• Not a replacement for Netlify or Vercel if you're already there — GitHub Actions integration covers basic deploy-on-push, but serverless functions, preview environments, and the full branch-based preview workflow aren't here; if those are load-bearing in your setup, Static.app won't replace them.
• Tight free tier — one site and 50MB caps are real limits; a second project or a media-heavy site means upgrading, and the free tier has no room to grow into.