Log in
ZeRaLD is proprietary, self-hosted website deployment and server-management software designed to make creating websites and web applications with AI easier. The ZeRaLD deployer/server manager is installed on and runs from your own Ubuntu VPS, alongside the infrastructure you control. Build with the AI you prefer, deploy to your own server, and keep control of the server and release process.
Yes. ZeRaLD is designed to sit between AI-assisted development and your own server. You can create a website or application with an AI coding tool, then use ZeRaLD to prepare your VPS, deploy the project and manage later releases.
Not in the closed-platform sense. ZeRaLD does not force you to build inside one proprietary editor or use one AI provider. It is the deployment and server-management layer around the project you create, including projects made with AI.
No. ZeRaLD itself is proprietary software and is not an open-source project. That does not mean the deployer is a centrally hosted SaaS product: the ZeRaLD server manager/deployer is installed on and runs on your own VPS. ZeRaLD is built with and integrates open-source technologies and third-party components, but those components keep their own licences and do not make ZeRaLD open source.
Yes. Self-hosting is the normal ZeRaLD deployment model. The ZeRaLD server manager and deployer are installed on the Ubuntu VPS you choose and control. Your project, server-management environment and deployment workflow run on your own server rather than inside a ZeRaLD-hosted deployment platform. ZeRaLD being proprietary describes its licence, not where it runs.
Not in the usual hosted-platform sense. zerald.dev provides the public website, account and supporting services, but the server manager/deployer used to operate your VPS is installed on your own server. ZeRaLD does not require your deployed application or its deployment engine to live on centrally hosted ZeRaLD infrastructure.
ZeRaLD is not tied to one AI provider. The workflow is intended to work with the AI development tool you trust, including tools based on models such as GPT, Claude or Gemini, provided the tool can work with the project context you give it.
Yes. Mobile is a first-class way to use ZeRaLD, not a cut-down companion experience. The zerald.dev account area and ZeRaLD workflows are designed to work responsively in a mobile browser, so normal server, deployment and AI-assisted development tasks do not require sitting at a desktop computer.
Yes. A typical mobile workflow is to use your preferred AI on the phone, give it a temporary ZeRaLD AI development handoff when project context is needed, receive the resulting edited files or patch, and deploy through ZeRaLD's normal workflow. You do not need to review or apply multi-file Git patches in a phone terminal just to use the handoff flow.
No for the normal ZeRaLD workflow. The interface is designed so that creating or managing a server, checking a project, using AI handoff and deploying releases can be handled from a mobile browser as well as a desktop browser. A larger screen may still be more comfortable for unusually detailed manual code review or advanced diagnostics, but it is not a requirement for ordinary use.
No. Your website runs on the VPS you choose and control, and the ZeRaLD server manager/deployer is installed there too. ZeRaLD helps prepare, deploy to and manage that server without moving the application or deployment engine into a ZeRaLD-hosted environment.
You need a clean VPS running Ubuntu. ZeRaLD is not locked to one Ubuntu version; a currently supported Ubuntu LTS release is recommended for a production server. A clean image is preferable to a VPS preloaded with a hosting panel or application stack.
ZeRaLD is provider-independent: the important requirement is a suitable clean Ubuntu VPS, not the company selling it. The installer currently points newcomers toward Contabo as the project owner's personal value-to-features suggestion, with Hetzner and Vultr as other examples.
ZeRaLD is specifically intended to reduce the amount of routine terminal and server administration needed to get a project online. Advanced tools and diagnostics can still exist when they are useful, but understanding nginx commands should not be a prerequisite for publishing a website.
The automated installer needs the connection details for the Ubuntu VPS itself. For a normal password-based fresh VPS this is usually the server username root and the root/server password supplied or configured for that VPS — not the username and password for your hosting provider account.
ZeRaLD inspects the project, prepares the server around the application, builds and verifies a candidate release, and promotes the release when the deployment succeeds. The release workflow is designed to preserve a working live release when a replacement fails.
ZeRaLD is built around real web projects rather than a proprietary page format. Its project and runtime tooling is intended to recognise the application and prepare the ordinary server tooling and language runtimes that project requires.
AI handoff lets you share selected, temporary, read-only project context with an AI development agent. The server decides the shared boundary, the handoff expires, and deployment remains a separate ZeRaLD action rather than giving the AI unrestricted control of the server.
You do. ZeRaLD's model is based on bringing your own VPS. The server and deployed website remain on infrastructure you choose rather than being moved into a ZeRaLD-only hosting environment.
No. AI is one branch of the workflow, not the whole product. ZeRaLD can still be used as the deployment and server-management layer for projects developed without AI.
Zee is the small, curious ball of fluff that lives around the ZeRaLD website. Zee is part of the character of the project, not a requirement for deployment or server operation. How Zees move, and what is underneath the fur, remain unverified.
Waking Zee up…
