Support
We built it so that you can install and use it on your own. When you need to combine multiple machines, move what you already use, or have no one to look after it, we come to you.
When to contact us
| If this is your situation | |
|---|---|
| Services must stay up even if one server dies | Cluster setup |
| You don't know what can be moved from the cloud you use now | Migration consultation |
| You haven't bought hardware yet — what specs should you buy | Spec selection |
| It's installed, but no one on the team can look after it | Operations support |
| Your network is isolated or outbound traffic is blocked | Every environment differs, so we check first |
If it's not listed above, you can usually do it yourself. Common sticking points are collected in Advanced.
Included in the beta
Based on a single server, the following works as is, without contacting us.
| Installation | The installation wizard deploys onto a single server → Chapter 2 |
| Asset installation · connection | Pick from the Catalog and even the connection details are plugged in → Chapter 5 · Chapter 8 |
| Addresses · HTTPS | Issuance and renewal are automatic → Chapter 9 |
| Login | Installed services open with a single account → Chapter 3 |
| Asset backups | Schedule · Retention period · Restore |
| Metrics · Logs | Populated once you install observability from the Catalog |
What we do
| What | Prerequisites | |
|---|---|---|
| Cluster setup | A multi-machine configuration where services stay up even if one machine dies — datastore switchover · joining nodes · a representative address · cluster snapshots | 3 nodes · fast disks (NVMe recommended) for data storage |
| Migration | We look at what can be moved from the cloud you use now, move it, and hand it over to you | — |
| Spec selection | Server specs and expected costs suited to what you want to do | — |
| Installation on your behalf | Up to deploying onto your hardware | — |
| Operations support | Upgrades · dashboards and alert rules · incident response contact | Annual |
Why cluster setup needs 3 nodes — with two, you can't determine which one is the one still alive. With three, a majority vote is possible.
Disks are listed separately because this configuration adds an option to manage a single disk as a cluster. Without an RWX disk cluster, it's hard to get proper performance even with multiple nodes.
How it works
| 1. Contact | Tell us what you use now and what you want to move |
| 2. Configuration proposal | Required specs · scope of what can be moved · expected costs |
| 3. Build · handover | We build it and hand it over in a state you can operate |
Contacting us is not a contract
You can ask about spec selection alone. Many start by checking what is reduced, and by how much, in their current cloud.
Contact
| Contact | info@tidoly.com |
|---|---|
| Consultation topics | Server spec selection · Migration from existing cloud · Installation on your behalf · Cluster setup · Operations inquiries |
What the product handles for you → Features