Static sites, from your source to your domain.

Publish from Git, the CLI, or a ZIP upload. We serve the files, manage TLS, and keep your deployments in one place.

  • EU hosted
  • TLS encrypted
  • German data centers

Starter plan: €2.99/month for your team, excluding VAT.

From source to site

Source
Git repository, built ZIP, or CLI push
Build command and output
npm run builddist/Example settings. Use your project's build command and output directory.
Your address
my-site.pages.danubedata.roAn example subdomain, ready for your own custom domain.

What customers say

“As a developer and cloud enthusiast, I’ve tried a lot of infrastructure platforms — but DanubeData genuinely stands out as one of the most intuitive, modern, and reliable cloud services I’ve used. From signup to deployment, everything feels thoughtfully designed and developer-centric. Deploying a VPS, cache, or database instance takes under a minute — and that’s not an exaggeration! Their intuitive dashboard and instant provisioning make launching new services effortless, even if you’re just getting started with cloud infrastructure”

Keoma WrightCEO/Founder at OpenWeb.co.za
Cristian TorzsaCEO at InnovaSoftware SRL
Bo PereiraParis-Brest srl
Read more customer stories

Three ways to publish

Choose the workflow that fits your project. Every method publishes the same static site.

Git auto-deploy

Connect a GitHub or GitLab repository, choose a branch, and deploy when you push. Configure a build command and output directory for your site.

ZIP upload

Upload an archive of your built HTML, CSS, JavaScript, and assets. A direct path for an existing site or a local build.

CLI push

Push your built files from the terminal with the danube CLI. Use the same workflow in scripts and CI pipelines.

Explore CLI push

Source, build, publish

  1. Choose your source

    Connect a repository and branch, or upload files you have already built through ZIP or the CLI.

  2. Build and deploy

    For Git builds, set the build command and output directory. Follow the build and deployment from your dashboard.

  3. Connect your domain

    Use your pages.danubedata.ro subdomain or add a custom domain. Verify your DNS settings and let us provision TLS.

Keep the site in your hands

Manage the address, access, and published version without operating a web server.

  • Custom domains

    Give your site its own address. Add a domain and verify its DNS settings from the dashboard.

  • Automatic TLS

    HTTPS for your site subdomain and verified custom domains, with managed certificates.

  • Deployment history

    Keep track of published versions and activate a previous deployment when you need to roll back.

  • Password protection

    Enable basic authentication for client previews, staging sites, or internal documentation.

Read the Static Sites documentation or explore the REST API.

A plan for your team's sites

One team plan, with storage and custom-domain limits for each site. Automatic TLS and all three deployment methods are included. Account limits may lower the site count.

Free

For personal projects and experiments.

Free

Sites per team
2
Storage per site
100 MB
Monthly bandwidth
10 GB
Custom domains per site
2

Monthly prices exclude VAT.

Built for static output

Bring your generator, framework, or plain HTML. Publish the files it produces.

  • Portfolios and personal sites

    Publish your work, a resume, a photography portfolio, or a personal blog.

  • Documentation

    Host VitePress, Docusaurus, MkDocs, or another generator that produces static files.

  • Landing pages

    Publish product launches, campaign pages, event sites, and coming-soon pages.

  • Statically exported apps

    Deploy static output from Next.js, Nuxt, Astro, or SvelteKit. Apps that need a running backend belong on Rapids or a VPS.

Questions about Static Sites?

Builds, deployments, domains, and plans.

Need help with your project? Ask us.

  • Static hosting serves pre-built HTML, CSS, JavaScript, and assets. It suits portfolios, documentation, landing pages, and statically exported apps. If your application needs a running backend server, choose Rapids or a VPS instead.

    Link to this answer

Your site. Your domain. Your workflow.

Connect your source, publish your files, and manage the next deployment from the same place.