Self Hosting
Why We Chose Independent Hosting
We control the organization's work and future
Most modern websites no longer operate as independently hosted systems. Instead, they exist within large platform ecosystems or software-as-a-service environments where the organization does not fully control the underlying infrastructure.
In many cases, this arrangement is convenient. Hosting, maintenance, updates, backups, security, analytics, publishing tools, email systems, and other services are bundled together into a single subscription platform. Organizations can often launch websites quickly without needing to understand how the infrastructure functions internally.
At the same time, this convenience often comes with tradeoffs. Organizations may become dependent on proprietary systems, recurring subscription costs, outside vendors, advertising ecosystems, tracking systems, or technical environments they cannot realistically maintain or move independently.
For Saving Birds Thru Habitat, maintaining a greater degree of control over the website infrastructure was an important goal from the beginning.
“We wanted the organization to own its publishing infrastructure rather than merely renting access to it.”
The website is hosted using relatively traditional open web infrastructure built around open-source systems and independently managed hosting rather than a fully centralized publishing platform.
This does not mean the organization owns physical servers or operates a datacenter. Rather, it means the website itself remains portable, understandable, and maintainable outside the control of any single commercial ecosystem.
The website files, images, templates, databases, newsletters, exports, and publishing systems can all be backed up directly and moved if necessary. The organization retains direct access to the underlying structure of the site rather than interacting only through a proprietary interface.
This approach also supports the broader philosophy running throughout the project: reducing unnecessary dependency, preserving autonomy, maintaining clarity, and building systems capable of remaining stable over long periods of time.
Independent hosting also aligns naturally with the hybrid publishing model used throughout the website. Because the public-facing site is exported as static HTML files, the infrastructure requirements remain relatively modest. The public website does not require a large continuously operating application stack simply to serve ordinary pages to visitors.
There are disadvantages to this approach. It requires more direct responsibility, more technical understanding, and more long-term organizational involvement than simply subscribing to a fully managed platform. However, it also provides greater independence, transparency, portability, durability, and control over how the organization communicates and publishes its work.
The goal is not technological purity or isolation from modern systems. The goal is to build infrastructure that remains understandable, maintainable, and aligned with the long-term needs of the organization rather than becoming dependent on systems it cannot meaningfully control.
One important aspect of independently managed hosting is direct access to the underlying system itself. Through the file manager and terminal, the organization can directly inspect the website files, exported HTML pages, templates, images, backups, logs, and publishing scripts.
This level of access is increasingly uncommon in modern platform-based publishing systems, where organizations often interact only through a restricted web interface while the underlying infrastructure remains hidden from view.
“We wanted the website to remain inspectable, understandable, and repairable.”
Direct access to the filesystem and server environment makes it possible to back up the site completely, move it if necessary, automate publishing tasks, inspect generated files, diagnose problems directly, and understand how the system actually functions.
That transparency reduces dependency on proprietary systems and helps preserve long-term organizational autonomy. The website remains a real collection of files and systems under direct organizational control rather than existing only as an abstract service provided by an outside platform.