The interface is often built for infrastructure people.
Businesses end up learning hosting terminology just to perform routine tasks.
Product
Clovora
Put the business online. Keep the infrastructure out of the way.
Clovora is the hosting and cloud product we're building for websites, applications, email, domains and the infrastructure businesses depend on to stay online.
Product site coming soon
See what we're building
01
What Clovora is
Hosting should help a business get online, not turn the business into a hosting expert.
A business needs somewhere reliable to run its website, application, email and related services. Most of the time, the business does not want to spend its day thinking about control panels, server terminology or infrastructure decisions.
Clovora is being built to make those everyday hosting jobs easier to understand while still giving developers the tools they need when the work gets more technical.
02
Why we're building it
Hosting is essential, but the experience is often harder than the job.
Buying hosting is only the beginning. Businesses still have to connect domains, install applications, manage email, keep SSL working and understand what to do when something needs changing.
Domains and hosting feel like separate products.
Connecting the address people visit to the hosting behind it should be straightforward.
Simple deployments can become support tickets.
Installing a website or putting an application online should not require unnecessary back-and-forth.
Growth eventually changes what the business needs.
The hosting experience should have somewhere to go when a basic website becomes a more serious application.
03
What Clovora brings together
The common pieces of getting a business online should live close together.
Clovora starts with the things businesses and developers regularly need around hosting. The aim is to make those pieces feel like one product instead of unrelated tools.
Web hosting
Hosting for business websites and the applications behind them.
Domains
Search, registration, transfer, renewal and nameserver management as the product matures.
Business email tied to the hosted domain without forcing customers into another provider.
SSL
Keep websites on HTTPS without making certificate management a daily concern.
Developer tools
Git, terminal access, cron and the practical tools needed to maintain applications.
Application runtimes
Support for common web stacks as Clovora grows beyond basic website hosting.
04
The Clovora console
Customers should manage hosting from Clovora, not feel like they were dropped into somebody else's control panel.
The console is meant to put the common jobs first: create hosting, connect a domain, manage email, inspect usage and get to the tools needed for the application.
Underlying infrastructure can change over time. The customer-facing experience should remain recognisably Clovora.
05
From code to something people can use
The deployment path should be easy to follow.
Whether the customer is putting up a business website or deploying an application, the steps should make sense without requiring them to understand the whole infrastructure stack.
Choose what to host.
Create the hosting space for the website or application.
Bring in the code or site.
Install the application, deploy from source or use the tools available for the stack.
Connect the domain.
Point the address customers will use to the hosted project.
Secure it.
Keep the website or application available over HTTPS.
Keep it running.
Manage the practical hosting tasks as the project changes over time.
06
Built for more than one kind of customer
A business owner and a developer should not need the same screen for every task.
Clovora needs to be approachable for someone who just wants a website online while still being useful to somebody who wants direct access to application tools.
Businesses
Host the company website, domain and email without living inside infrastructure settings.
Agencies and freelancers
Manage websites and projects for customers from a cleaner hosting experience.
Developers
Use the tools needed to deploy and maintain applications without losing the simpler management layer.
Growing applications
Have a path from straightforward hosting toward more capable cloud infrastructure as requirements change.
07
Where Clovora is heading
Start by making hosting easier. Build deeper cloud capability over time.
Clovora does not need to pretend to be a giant cloud platform on day one. The immediate job is to make hosting, domains and the common deployment tasks work well. More infrastructure capability can grow from there.
Make hosting understandable.
Give businesses and developers a clean way to get sites and applications online.
Bring more of the workflow into one console.
Domains, application tools, email and management should feel connected.
Own more of the cloud layer.
Build the infrastructure needed to support more runtimes, databases and application workloads directly.
08
How we want the product to feel
Infrastructure underneath. A straightforward product on top.
Do not expose complexity just because it exists.
The interface should show the customer what they need for the job they are doing.
Keep common tasks close.
Domains, email, SSL and application management should not feel like separate products.
Give developers real tools.
A simpler interface should not mean removing the capabilities technical users actually need.
Leave room to grow.
The product should make sense for a first website and still have a direction when the workload becomes more serious.
Clovora