Astro cloud hosting # Astro hosting for static sites Build Astro content sites, blogs, and documentation with static output. Deployment is currently paused while service provisioning is unavailable. [Get started](https://panel.deplomo.com/signup)[Astro deployment guide](/guides/deploy-astro) ## Astro hosting features Use Astro’s static output and supported framework integrations. Build behavior and performance depend on your project configuration and package limits. ### Git-based deployment Connect a GitHub or GitLab repository to build and deploy Astro site updates when a push triggers the configured workflow. Service creation and deployment are currently paused. ### Astro Islands architecture and JavaScript output Astro can limit client-side JavaScript to interactive islands. Page speed and Core Web Vitals depend on the site, assets, and configuration. ### Static output and server-side rendering Astro supports static generation and can use SSR adapters for server-rendered pages. Confirm that your adapter and runtime match the deployment target. ### Custom domains and SSL The platform provides a service subdomain. Custom-domain and certificate availability depend on current platform configuration; service creation is currently paused. ### Package installation and external integrations Install npm packages and connect an Astro project to a headless CMS or external API when the required credentials and network access are configured. ## Frequently asked questions about Astro hosting Answers to common questions about Astro deployment, static output, SSR, domains, and environment variables: Which Astro output modes can I use? What types of websites can I build with Astro? Can I use React or Svelte components in Astro? How do I configure a custom domain and SSL for Astro? Is there a free plan for Astro hosting? ## Astro hosting guide: building and serving Astro sites Astro is designed for content-focused sites and can limit JavaScript sent to the browser. Its Islands architecture lets you add interactive components where needed. Deployment behavior and performance depend on your project and configuration. Deplomo’s Astro stack currently serves static build output; service creation and deployment are paused. ### What is Astro, and how does it fit into web development? Astro is a web framework often used for content sites, blogs, documentation, and landing pages. It renders pages as HTML and CSS by default, while client-side JavaScript can be added for interactive components. Astro works with components from other frontend ecosystems. For highly interactive admin panels or single-page applications, frameworks such as [React hosting](/products/react) or [Svelte hosting](/products/svelte) may also suit your project. ### What should I consider when deploying an Astro project? With traditional shared hosting, you may need to build the project locally, upload the output, and configure routing yourself. The steps depend on the hosting setup and your project. A Git-based build workflow can install packages and run a configured build in a container when deployment is available. For sites that are already built and ready to serve, [Static hosting](/products/static-sites) Deplomo’s static-site service is another option. Service creation and deployment are currently paused. ### Astro deployment approaches compared This table summarizes common differences between a configured Astro service, shared hosting, and a self-managed server. Actual features depend on the selected provider and setup:

Feature	Deplomo Astro service	Conventional shared hosting (cPanel)	Unmanaged VPS
Build and deployment workflow	Git-based build and deployment when enabled; currently paused	Manual upload of locally built files, often via FTP	Configure and maintain your own Git, build, and webhook workflow
Astro output mode	Static output is served by the current Astro stack; verify SSR requirements separately	Often serves static files; runtime support depends on the host	Configure and maintain a compatible Node.js runtime and web server as needed
Build environment and package installation	Container-based builds; package access depends on the environment and registry	Build tooling may need to be configured or run locally	Build environment and package access depend on your server configuration
Custom domains and certificates	Certificate support and automation depend on the platform and domain configuration	Options depend on the hosting control panel and its configuration	You manage certificate issuance and renewal for your server
Pricing and cost visibility	Plan and billing model	A Free plan has a 256 MB resource limit; paid Hobby and Pro plans use fixed monthly EUR pricing	Pricing and term options vary by provider
Server and network costs depend on your provider and configuration	Capacity and availability	Capacity depends on the selected plan and configuration	Capacity depends on the hosting plan and configuration

Compare the build workflow, runtime support, plan limits, and domain options before choosing an Astro host. Availability depends on the provider and service status. ### How to prepare and deploy an Astro project on Deplomo For current setup details, see the guide at [Deploy Astro](/guides/deploy-astro) . The usual workflow is: - **Connect a Git repository:** Sign in to the Deplomo console and select a GitHub or GitLab repository if the integration is available. - **Choose a deployment branch:** Select a branch such as main or production. Automatic deployment depends on the configured workflow and is currently paused. - **Configure environment variables:** Add required configuration values in the environment-variable settings. Keep secret values private and do not expose them in client-side code. - **Build and deploy the service:** The platform can build the project in a container when deployment is available. Service creation and deployment are currently paused. The Deplomo Free plan may suit small projects that fit within its resource limits. See [Free high-speed hosting](/free-host) for details; the plan has a 256 MB resource limit. Service creation is currently paused, and no trial wallet credit is provided. ### How Astro can affect website performance and search visibility Astro’s static output and limited client-side JavaScript can be useful for content-focused sites. Actual page speed, accessibility, and search performance depend on the site and its configuration. - **HTML output for indexing:** Static HTML can help search engines process page content. Indexing and rankings are not guaranteed. - **Image optimization:** Astro integrations or build tools can optimize images when configured; confirm which tools your project uses. - **Deployment region and network:** Network latency depends on the service location, route, and user. No latency or delivery guarantee is implied. - **Package registry access during builds:** Package installation depends on registry availability and the build environment’s network configuration. ### Preparing an Astro project for deployment Astro is often used for content sites and business pages, with static generation and integrations available through project configuration. Deplomo supports Astro static build output; domain, certificate, plan, and deployment options depend on current platform availability. Review the Astro deployment guide and check service availability before planning a deployment. ## Publish your Astro website Review Astro’s static output and prepare a Git repository for deployment when service creation and deployment resume. [Astro deployment guide](https://panel.deplomo.com/signup)