Just launched Velyr - solo project, a few months in the making
Shipped this two days ago.
Velyr started as a simple question: why do audit tools give you a report and then leave you to figure it out yourself?
Three things I built:
-
Free scan: enter any URL, get an audit in 60 seconds. No account needed. Checks SEO basics, mobile UX, CTA placement, page speed and social presence.
-
Full Report (9€ one-time) : deeper dive with real data pulled from your social channels and Google PageSpeed. Everything scored and prioritized so you know what to fix first.
-
Growth Agent (29€/month): runs every Monday, finds the biggest conversion problem on your site, writes the actual code fix, opens a GitHub PR. You get a Telegram message with the problem, the fix and the PR link. Reply YES to deploy, NO to skip. Auto-rollback if metrics drop after a deploy.
Stack: React/Vite, Supabase, Vercel, Anthropic API, Apify, Telegram bot. Works with React, Next.js and Vite projects on Vercel.
Hardest part wasn't the tech - it was the legal side as a solo founder in Germany. Took way longer than expected.
Revenue: 0. Day three.
One thing I'm genuinely unsure about: is €29/month the right entry price for the agent, or does that feel too high before there's any social proof? Would love to hear from anyone who's priced something similar.
The strongest part here is the Growth Agent, not the audit. A free scan and report are useful, but they still sit in the crowded “website audit” category. The real wedge is that Velyr doesn’t just tell the founder what is wrong. It finds the highest-impact conversion issue, writes the code fix, opens the PR, and lets them approve deployment from Telegram.
That is much sharper than “audit tool.” I’d position it closer to a weekly conversion engineer for small teams using React, Next, Vite, and Vercel. The pricing also makes more sense if the buyer sees it as an agent that ships fixes, not a report generator.
One thing I’d watch is the Velyr.io brand. Velyr is clean, but if this becomes a broader site-growth/workflow agent, Xevoa.com would give it a stronger platform feel and remove the .io trust friction early.
Thanks, the "conversion engineer" framing is sharper than how I've been describing it. The audit is really just the entry point. The agent finding the issue and shipping the fix is the actual product. Going to rethink the copy around that.
On Xevoa: not switching domains at this stage, but noted.
One practical thought.
Since you are already rethinking the copy around the Growth Agent, this may be the right moment to pressure-test the positioning properly before more users, docs, and onboarding build around the audit-tool frame.
I do focused naming/positioning audits for early products: current category risk, domain/extension perception, buyer-facing positioning, what the product currently sounds like, and what stronger frame would make the offer easier to understand and buy.
For Velyr, the key question is probably whether the product should be positioned as a website audit tool, a growth agent, or a weekly conversion engineer for small teams that actually ships fixes.
Not a long consulting thing. Just a sharp written breakdown with practical recommendations.
I’m doing a few of these at $99 while refining the format. If useful, connect here and I can put together a clear outside read for Velyr:
https://www.linkedin.com/in/aryan-y-0163b0278/
That makes sense. I would not force a domain switch before the product motion is proven.
The only distinction I’d keep in mind is that Velyr.io works fine while the product is still being understood as an audit-plus-agent tool. But if the “conversion engineer” frame becomes the main thing, the product starts feeling less like a utility and more like an execution layer for small teams.
That is where the brand and extension start mattering more.
If founders are trusting it to open PRs, change production code, and improve conversion every week, the name has to carry platform-level trust, not just tool-level clarity.
So I’d treat Xevoa less as a “switch now” idea and more as the kind of cleaner .com direction to pressure-test before Velyr gets deeply attached to docs, users, PR workflows, and customer memory.