About Hostingsurge

One product. Zero vendor noise.

Hostingsurge is an AI-first platform for websites, apps and hosting. The goal is deliberate: a person who is not technical should be able to describe what they want, get it built, run it in production — and still own it.

What we are building

Not a control panel with an AI button bolted on. One platform where the same concepts cover building, running and owning a project.

Websites and apps with AI

Describe what you want and get a real, working website — generated as code, checked on desktop and mobile, and repaired before you ever see it.

Hosting that fits the project

Static sites deploy statically. Code projects (React, Vite, Astro, Next.js) get the runtime they need. Nothing is provisioned that the project does not use.

Managed private source

Every project gets private version history and the UI speaks in versions, restore, compare and export — not in Git commands.

WordPress, safely

Managed WordPress plus a scoped connector for editing an existing site, with snapshot, staging, approval and rollback in the loop.

Migrations instead of rewrites

Bring a project from Vercel or Lovable, or a database from Supabase, with a compatibility report before anything is switched over.

Backend, storage and domains

Accounts, databases, object storage, domains and DNS appear as Hostingsurge features when a project actually needs them.

Agents and one-click apps

Managed AI agent runtimes and a curated application catalog, provisioned with isolation rules rather than privileged containers.

An API and MCP access

The same platform, reachable by your own tools — scoped to an organization, a brand and a project, never to the whole platform.

Usage-based billingWhite-label national brands on one shared backendExport at any timeEnglish and Swedish from day one

How it is built

These principles are not aspirations — they are the reason the product looks and behaves the way it does.

Static first

A generated site is never given a database or a permanent process merely because AI wrote it. If it can be static, it is static.

Backend on demand

Logins, persistent records, private uploads, scheduled jobs and private APIs create backend resources. Nothing else does.

The platform abstracts providers

Deployment, source, storage, domains, payments, AI and email each sit behind an adapter. You work with Hostingsurge concepts; the vendor names never reach your screen.

One portal

Normal workflows never send you to a third-party dashboard. If a task exists, it exists inside Hostingsurge.

White-label from day one

Every request belongs to a brand. Domains, names, design tokens, languages and currencies are brand configuration, not hardcoded product logic.

No lock-in

Your code, your versions, your data and your domain stay yours, and export is a product feature rather than a negotiation.

Where the platform is today

A development preview. The honest split matters more than a launch date.

Implemented and verified

  • Identity: accounts, email verification, sign in and out, password reset, TOTP MFA with recovery codes, sessions and tenant resolution.
  • Teams and access: six roles, invitations, project grants, and API and MCP credentials with explicit scopes, lifetimes and revocation.
  • Projects and source: managed projects, immutable source versions, comparison, restore and ZIP export.
  • Isolated builds: a no-network sandbox, hash-verified artifacts, append-only receipts and durable workers with fenced leases.
  • AI core: a model registry with task routing, an OpenRouter adapter, budget guards and the builder pipeline from plan to preview-ready state.
  • Billing backend: a durable credit ledger, verified top-ups and subscription fulfillment, refunds and disputes.
  • Customer surface: landing, onboarding, account overview, projects, project view, versions, source browser, teams, keys, AI policies and billing.

Specified, not shipped

  • Domains and DNS purchasing, transfers and DNS management.
  • Managed WordPress hosting and the WordPress connector.
  • App store, AI agent instances and backend provisioning as customer-facing modules.
  • Usage metering, the admin surface and the setup wizard.
  • Publishing and custom-domain activation through the deployment provider.
  • Monitoring, alerting and a real status history.
  • Live payments: no price catalog is published and no checkout is enabled.

Languages and markets

Built multilingual and multi-brand from the start, not translated at the end.

  • The customer surface ships in English and Swedish, with full parity between the two.
  • The specification’s multi-brand engine lets national brands share one backend without forking the frontend: brand resolution happens on the host, and a cloned brand gets its own domains, design tokens, prices, language and legal copy.
  • Each national site is meant to carry genuinely localized currency, pricing, support and market content rather than duplicated copy.

Why this page stays plain

A company page is easy to fill with things that are not true yet.

There are no customer logos here, because there is no published customer list to show.

There are no testimonials, ratings or adoption numbers here, because none exist to cite.

There are no team biographies or funding announcements here, because those are not facts this page can establish.

There is one honest ask: if the platform is not where you need it to be today, use the status and docs pages to see exactly where it is — and come back when it is.

Describe it. Build it. Own it.

Create a free account and take the first project through onboarding and versions.

This is a development preview. Modules not listed as implemented are still being built, and this page will say so until they are not.