Frontend Cloud: Build from Git.
Publish at the edge.

Frontend Cloud builds a frontend project from your Git repository and publishes the compiled output to a global content delivery network. It suits React, exported Next.js, Vue, Angular, Svelte, Astro, and any project that produces static files. Each subscription covers one project.

Connect GitHub, GitLab, or Bitbucket, or deploy from a public Git repository URL. You choose the branch, and you can deploy the latest commit or a specific commit.

You set the branch, the root directory for a project inside a monorepo, the build command, and the output directory that gets published. You can also clear the build cache when a dependency change needs a clean build.

Yes. Set the root directory to the sub-path that contains the frontend project, and Darwa runs the build from there rather than the repository root.

Previews can be created automatically or manually, and filtered by pull-request label or base branch. Previews expire after 72 hours by default, and up to 3 can be active at once — configurable up to 20 — so open pull requests cannot quietly consume your build minutes.

Yes. Every project receives a Darwa endpoint as soon as it deploys. Add a verified custom domain and TLS certificates are issued and renewed automatically, with the certificate and routing state visible in the dashboard.

Three edge cache profiles: no cache, static assets only, or aggressive. Frontend Cloud also respects the Cache-Control headers your build emits, so an application that already sets its own caching policy keeps it.

Transfer, requests, build minutes, and storage are metered against your plan's allowance. You can set a usage-alert threshold — 80% by default — and an optional monthly budget. With budget pausing enabled, Darwa stops starting new builds at the limit rather than accruing overage.

Each plan publishes a per-unit overage rate for transfer, requests, build minutes, and storage. The dashboard shows current usage against the allowance before any overage applies, and a monthly budget can pause new builds instead.

No. Frontend Cloud publishes compiled static output, so it cannot run a server process, server-side rendering at request time, or API routes. Use Darwa Web Services for a continuously running application or API, and Web Hosting for PHP, WordPress, and Node.js websites.

All three build from Git and serve from a global edge network with pull-request previews and managed TLS. Frontend Cloud is deliberately scoped to static output, and it sits in the same workspace and invoice as Darwa databases, object storage, background workers, and business email. If you need serverless or edge functions, image optimisation, or request-time server rendering, those platforms cover cases Frontend Cloud does not.

Yes. Connect the repository and deploy to the Darwa endpoint while your current host still serves live traffic. Verify the build, then point your domain at Darwa; TLS is issued once the domain resolves.

Frontend hosting supports static output from React, exported Next.js, Vue, Angular, Svelte, Astro, and other generators. That makes the service suitable for React app hosting, Next.js hosting for static exports, Vue app hosting, Astro hosting, and framework-independent static site hosting.

Yes for static output. Darwa is a Jamstack hosting and edge deployment platform that builds from Git and publishes compiled assets to a global CDN. It does not run request-time server rendering or edge functions; those workloads belong on Web Services or Web Hosting.

Yes. You can deploy a static site free on the available Frontend Cloud free tier, connect the repository, and test the generated Darwa endpoint before choosing a paid plan. Current transfer, request, build-minute, and storage allowances are shown in the pricing table.

Yes. Global CDN hosting is the delivery layer for every Frontend Cloud project. Darwa builds the selected commit, publishes the output directory, applies the configured cache policy, and serves it over managed HTTPS from the project endpoint or your verified custom domain.