Hey Folks,
Just wanted to update everyone on where things are going.
A lot has changed since I first put this project together, however I feel the changes are for the best.
Over the last number of months I’ve been designing control panels for usage with my various services, some that have been around for a while and others which are emerging or are intend to emerge shortly.
What I’ve been learning throughout this process is that making a UI which people are familiar with is super important. It’s not only important to make the UI easy to navigate (similar to cPanel in this sense) but also maintain your brand along the way, and most important ensure that the UI is designed with a consistant flow.
As a result, I started using the same theme across my various control panels and have been working toward linking them both in terms of maintaining a central client database, but also allowing you to switch between panels with a simple click of a link.
The goal is to make all services available to all users, but only allow the users to use the services which they have an open subscription for, and finally allow them an easy way to find out about new services offered, while enabling the ability to sign up for new services directly from the panel.
Ex. you sign into our billing portal and notice a tab for new service is available, along with perhaps a notice advertising the new service. You click on the new tab, and are presented with a sign up form allowing you to take advantage of the new service within minutes.
Now, getting back on topic here…
The direction I’m going with the project is to build more of an “API” and a number of background processes which are linked to it.
As someone recently discussed, the topic of building more than a simple hosting panel is in fact part of what I’m aiming to offer. The ability to run a full set of services from the panel is my goal.
While I realize a number of you want access to source code so you can implement things on your own network, I’m thinking of targeting the service to run “in the cloud” and have our servers communicate with your servers managing the provisioning through an SSH session (using a custom private/public key pair).
the advantage to YOU:
-
You would be able to build a custom UI around your own brand without exposing that you are using our technology (unless you want to)
-
All updates would be handled on our end allowing for you to take advantage of new features and security updates immediately as they become available.
-
Assistance would be offered in both a forum design allowing p2p support, along side direct support from me when needed.
-
The price to take advantage of our API would be tiered and affordable for all.
The advantage to ME:
-
I would be able to maintain a single code base which could then extend to any number of users without having to know your sysem architecture specifically.
-
I would be able to field updates, and security issues in bulk without having to release and support individual client.
-
I would retain the source code and rights to my infrastructure without having to charge insane prices or having someone resell my code as their own.
I’d welcome comments, feedback, and suggestions to the above idea and will further elaborate on things as they progress.
I hope I have not turned away a number of you in making a slight change in direction, and appreciate any and all feedback provided on the overall project.
-Peter