A web hosting control panel with a social network you say?

We are dreamers. We like to build things in our own unique style. We aim to provide a different kind of web hosting. We operate a ‘hosting platform’, not just a ‘hosting control panel’.

Our current hosting dashboard already includes collaboration features. It helps startups, agencies and freelancers to map their real world business relationships, so they collaborate with each other and their clients. These features are used a lot. Many other hosting providers have also integrated similar functionality by now.

So for the new platform in the making I explored how to improve those existing collaboration features and solve some quirks and shortcomings along the way. It became a big undertaking. Foremost, the data structure had to change. Most top down hierarchy had to be replaced with many-to-many relations to offer the flexibility I aimed for. There are only four kind of objects: people in relation to apps, teams and payment methods.

But it was hard. Make it powerful but not complicated. It took various attempts to get it right.

One approach had some unexpected results, changing billing should not change developer access. Another one was too leaky, imagine an open social graph to browser the apps of the colleagues of your colleagues.

Another challenge was to settle with restriction levels for the roles with the teams. What is allowed and what not? Can our tool help to prevent damage done by incautious junior developers or unaware clients? it turned out that even the lowest kind of possible access level implies that people collaborating with each other also need to trust each other. It’s impossible to make it bullet proof. We don’t want to ship something that only pretends to be secure.

We ended up with a open solution and only two simple team roles. Our solution should enable people to collaboratively create.

I think it will feel familiar for existing customers.

Hosting is about technical stuff, but also about people. Your account is your personal access to the platform. People can be part of multiple developer teams with different roles. Payment methods are owning the apps, they are managed by people.

You can invite others as solo developers to specific apps, or to one of your teams to participate on all or even just some selected apps. You can invite someone to a payment method or to take over billing. Non-technical clients have access to a slimmed down dashboard, excluding technical details. People can also request to get access on objects.

Overengineering? Certainly. 🚩🚩🚩