Hosting someone’s website is not like hosting a file. A website is someone’s creative work. Their business. Their community. Their years of effort. When they choose your platform, they are not choosing a service provider — they are choosing a steward.
That is the part of platform building no one talks about.
What trust demands
Trust demands that data remains accessible. That sites from ten years ago still work. That users who built on one version of the platform are not abandoned when the next version ships. That the person running the platform understands the weight of what they are carrying.
Trust demands that there is always an exit. That users can take their data and leave. That the platform never becomes a prison. That the code is open so users can verify what happens to their information.
Trust demands honesty about risks. That a small team has limitations. That self-hosting is an option and the documentation for it should be clear. That pricing changes are explained, not hidden.
How the community shaped this
This understanding did not come from reading about platform ethics. It came from years of listening to the people who use Wapka. A user whose site went down during a migration and needed it back urgently. A student who built their portfolio on the platform and was terrified of losing it. A community member who contributed server resources when infrastructure costs were straining.
Every one of these experiences taught me something about what it means to be responsible for other people’s work. The platform exists because of them. The responsibility exists because of them.
The principle
If you build a platform, you are not just building software. You are accepting a promise. The promise is: as long as this platform exists, your work will be safe here.
That promise is heavier than code. It is the foundation Wapka was built on.
Continue reading: Why I open-sourced Wapka → What’s coming: the roadmap →