diff --git a/website/landing/hub.html b/website/landing/hub.html index 20954dab..60ea0337 100644 --- a/website/landing/hub.html +++ b/website/landing/hub.html @@ -710,8 +710,7 @@
Your most-needed feature
- Something missing from this list? Tell us about your pain and it moves up the - queue.
+ Something missing from this list? Tell us about your pain. @@ -728,7 +727,11 @@Asked bluntly, answered bluntly.
++ Have another questions? Ask us on + Discord. +
- No. Uncloud is fully functional on its own, today, from the CLI. Hub adds a web UI - and an observability stack on top. If you never connect Hub, you lose nothing that - exists now. + No. Uncloud is open source + and fully functional on its own without Hub. You can use + the CLI to manage your clusters and deploy your apps across servers from Compose + files. Hub adds a web UI and an observability stack on top so you don't have to + build and manage it yourself.
@@ -766,7 +771,8 @@No, and no point pretending otherwise. Uncloud, the orchestrator, is Apache 2.0. Hub - is a hosted service built on top. + is a managed service built on top, and it's how we plan to fund Uncloud's full-time + development.
@@ -784,9 +790,10 @@Metrics and logs will flow to Hub. Storing, graphing, and searching them is the - whole point of a hosted observability stack. Your apps, code, and databases stay on - your machines. What exactly gets collected and how you control it is being designed - right now, with early access users. + whole point of a hosted observability stack so you can access them even when your + servers aren't available. Your apps, code, and databases stay on your servers. What + exactly gets collected and how you control it is being designed right now, with + early access users.
@@ -805,8 +812,9 @@The connection model is being designed right now with early access users. The intent is the minimum Hub needs to do its job: telemetry flowing out, and nothing - controlling your cluster unless you later opt into features like push to deploy. - Uncloud itself never stops working without it. + controlling your cluster unless you later opt into features like sharing access to + the cluster with your team or push to deploy. Uncloud itself never stops working + without Hub.
@@ -823,8 +831,8 @@- Nothing. Your apps run on your machines and Uncloud doesn't depend on Hub to - operate. Worst case, you lose the dashboard for a while. Not production. + Nothing. Your apps run on your servers and Uncloud doesn't depend on Hub to + operate. Worst case, you lose the dashboard for a while, not production.
@@ -841,9 +849,9 @@- You can. Grafana, Prometheus, and Loki are excellent, and they'll always work with - Uncloud. Hub is for people who want the graphs without adopting a monitoring stack - as a second hobby. If you enjoy running one, genuinely, carry on. + You can and if you do already, keep it. Grafana, Prometheus, VictoriaMetrics and + others are excellent, and they'll always work with Uncloud. Hub is for the day you'd + rather ship features than manage and monitor the monitoring stack.
@@ -860,9 +868,9 @@- No public date yet. Hub is in active development and everything on this page is a - design preview. Invites go to the early access list as pieces become usable. Pricing - isn't decided, and early access users will see it before anyone is charged a cent. + Hub is in active development and everything on this page is a design preview. + Invites go to the early access list as pieces become usable. Pricing isn't decided + yet, and early access users will get a discount for helping shape Hub.
@@ -880,11 +888,11 @@- Tell Pasha what you need Hub to do. The roadmap is short enough that one email actually - moves it. + Leave your email and we'll invite you as Hub becomes usable. Early users help shape it + and get a discount.
- No spam, no drip campaign. One person reads these. - Or email pasha@uncloud.run directly. +
+ Uncloud updates only, no spam. Or email + pasha@uncloud.run + directly.