Guides
Your website and ‘the app’ are not the same thing
Application hosts are for products that run code all day. A brochure site does not need that — and putting WordPress on one is usually the wrong save.
“Where should I host my startup?” threads are usually about application hosts: you ship code, they keep a process running, you point DNS at it.
That is the right shape for a product with logins, billing, and background jobs. It is usually the wrong shape for a five-page business website.
Two different homes
| What it is | Example | Typical home |
|---|---|---|
| A marketing / brochure site | Hours, services, a contact form | Builder on DevThunder, static hosting, or WordPress on a host we operate |
| An application | Accounts, checkout, an admin console | A platform that runs your code all day — or a dedicated app box |
Mix those up and you either overpay to run brochure pages like a startup, or you cram WordPress onto a platform that expects containers and hates PHP.
DevThunder itself is an application (the builder, the CMS, your account). Your public site does not have to live in the same kind of place. Most customers should never have to name an app host out loud.
What this means if you just need a website
- Start on **
*.sites.devthunder.com**. Share the link. It is real HTTPS. - When you want
yourbrand.com, that is Launch or quoted hosting — DNS, TLS, deploy. Not “create an app and hope the free tier stays awake.” - If you already have WordPress, we can care for it or move it. We will not park it on a sleeping demo box and call it hosting.
- If you are building a product (logins, payments, jobs), that is a different conversation — and a scoped project, not the Care add-on.
Why those ads keep showing up
Application hosts are good at always-on machines, git-push deploys, and pairing an app with a database. They are also good at surprise usage bills, and the free web tiers often sleep. Fine for a demo. A bad idea for anything you promise will be up on Saturday.
You need that map only if you are choosing an app host. For a shop site, skip to what launch actually includes.
How we split our own stack (the honest version)
Our marketing site and builder are an app: a CDN at the edge, a managed origin, a real database. Customer brochure sites we host are websites, not mini-copies of that app. We do not put your WordPress on the same box as our application. One incident should not take down both.
You do not need to recreate that architecture. You need a URL that works and a form that lands in an inbox you read.
Related: You do not need to shop for a VPS · Pricing
Was this useful?
Comments
Be the first to add a note.