VCloud's buyer is running from self-hosting. The homepage leads with the word "self-hosted."
Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.
Today: VCloud (varisymo.com), managed self-hosting for open-source apps.
Start with the sentence the founder wrote on Indie Hackers, because it is sharper than anything on the homepage: "running open source yourself is basically a second job." That is the whole business. VCloud is the company that takes the second job away. Nextcloud, GitLab, Rocket.Chat, all the tools a small team already wishes it could use, running for them with single sign-on, backups, and security patches handled, and nobody on the team ever paged at 2am. That is a real and valuable thing to sell.
Now look at what the homepage actually leads with: "Self-Hosted Applications Without the Complexity." The H1 opens with the two words that, to your buyer, mean the second job. An SMB with no IT team does not read "self-hosted" as freedom. They read it as the pager, the outage, the thing they pay SaaS to never think about. You spend the rest of the page walking back the promise your own headline made.
The lens is own the enemy, and the enemy here is not SaaS. It is the second job. This matters because your framing, "alternative to SaaS," picks a fight with the one thing your buyer actually likes. They did not choose Notion and Slack and GitHub because they love subscriptions. They chose them because those tools show up working and nobody has to run them. If you attack SaaS, you attack the convenience, and convenience is the exact thing you are selling. You are not the alternative to SaaS. You are SaaS economics for tools you get to own. Say that. Three moves.
Move 1: Rewrite the H1 as the outcome, not the architecture. "Self-Hosted Applications Without the Complexity" describes how the sausage is made. Your buyer wants the sausage. The headline should be the result they get to feel: your own GitLab, Nextcloud, and team chat, running for you, with no server to babysit and no per-seat bill that grows every time you hire. Put "self-hosted" lower on the page as the reason it is cheaper and yours, not as the first thing they see. This week, write three outcome-first headlines and test them against the current one.
Move 2: Aim the page at the buyer who signs the invoice, not the one who could set it up themselves. There are two people who might land here. One is a technical tinkerer who can already spin up a VPS and does not need you. The other is a founder or ops lead who is tired of renting eight tools, worried about where the data lives, and has no interest in touching a terminal. That second person is your customer, and they do not want to "self-host." They want to own their data and stop the subscription creep without hiring an admin. Name that dilemma in the hero. Once you speak to the buyer's problem instead of the builder's method, "self-hosted" stops being a warning label and becomes the proof that the promise is real.
Move 3: Pick the wedge before the platforms eat the easy half. One-click install of open-source apps is already commoditizing. Coolify does it, Railway and Render are close, and the OSS projects themselves keep shipping their own installers. If your pitch is "we make it one click," you are in a race you will lose to funded infrastructure companies. The half they will not touch is running it for a non-technical team as an ongoing service: the SSO nobody wants to configure, the backups nobody remembers to test, the patch that lands before the CVE does, and a human who owns uptime so the customer never learns what a reverse proxy is. That managed, we-own-the-outcome layer is your moat. Sell the babysitter, not the button, and price it like the second job you are absorbing, because that is what it is worth.
One risk worth naming, because it is the one that decides the ceiling: consumption pricing on compute invites a spreadsheet. A buyer who is comparing you to a SaaS subscription can also compare you to a raw VPS, and on pure compute the VPS wins every time. If the page frames the offer as cheap hosting, you lose to Hetzner. If it frames the offer as the second job removed, you are not selling CPU, you are selling the ops team they do not have to hire, and that is worth many times the compute. Guard the framing or the pricing will drag you into a commodity fight.
The forcing question, the one to answer before rewriting a line: if a buyer could keep only one of your two promises, "you own your data" or "you never touch a server again," which one closes the deal? One of those is a values pitch that a small slice of buyers cares about, and the other is a pain pitch that almost everyone with a growing tool bill feels. Whichever one closes, build the entire homepage around it, and let the other be the pleasant surprise on page two.
To VCloud: you already wrote the winning line, you just put it in an Indie Hackers post instead of your H1. The second job is the enemy. You are the company that takes it away. Lead with that, aim it at the person who signs, and own the managed layer the platforms will not touch.
Anyone else want their project run through the same lens? Reply with a link.
