Appwrite Sites: Zero to One

Appwrite provided a powerful backend, but once developers were ready to ship, they had to leave the ecosystem to host their frontend.

Sites was created to bridge this final gap, letting users host their applications without ever leaving Appwrite. My goal was to design a hosting workflow that eliminates context-switching and brings hosting into the same workflow.

The challenge was balancing instant deployment with the level of control experienced developers expect.

Instead of simplifying the interface, we moved complexity into the system. Once a repository is selected, Appwrite scans it to detect the framework and automatically pre-fills the deployment configuration.
Advanced settings remain available, but are surfaced only when needed.

The result is a deployment flow that goes from intent to production in three clicks without forcing upfront configuration decisions.

The core experience is designed to feel immediate and effortless from the first interaction. After connecting to GitHub, repositories surface instantly and the deployment wizard arrives prefilled.

For transparency, real-time build logs keep developers informed throughout. Advanced controls are there for those who need them, but the default experience stays fast and minimal.

Deployment is not the end of the experience, but the start of an ongoing feedback loop. The post-deployment experience was designed as a single operations layer for managing live systems, bringing together control, transparency, and observability in one unified interface.

The Site Overview serves as a control center, consolidating deployment status, previews, domains, and recent activity in one place. Every git push triggers a visual update in the dashboard, reinforcing that the system is active, responsive, and reliable.

For deeper inspection, deployment history, domain configuration, and live logs are accessible directly within the platform, providing full visibility without requiring context switching.

Sites introduced a new layer to Appwrite. A dedicated hosting service for developers, fully integrated into the ecosystem. This was not just a new feature but a new product surface that expanded how developers interact with the platform.

As this layer evolved, it influenced existing creation patterns across the console. Step-based wizards, originally designed for complex setups, began to feel misaligned with simpler and more modern workflows.

We introduced a fieldset-based creation model that replaces linear steps with a single continuous interface. This allows users to configure and complete setup without fragmented progression while still maintaining structure and clarity.

The result is a more unified product experience where the simplicity introduced by Sites extends beyond hosting into the core creation flows of the platform.