Run the writing, not the server
Self-hosting gives you total control and a standing maintenance job. Floggy keeps the parts that matter, the domain and the audience, and takes the upkeep off your desk.
- One domain
- Everything published under it
- No plugins
- Nothing to wire together
- API and CLI
- Publish from your terminal
The choice is upkeep, not quality
A blog you host yourself can do anything, and that is a real advantage rather than a talking point. It is also a small piece of infrastructure with your name on it, and infrastructure does not sit still. The runtime moves on. A dependency picks up a CVE. The build that worked in March quietly stops working in September. None of it is hard. It is just never finished.
What you are actually deciding
Both options produce a blog. The question is where your attention goes on the evening you sat down to write and found the deploy broken instead. Self-hosting spends that evening on the stack. Floggy spends it on the post, and hands you back less room to tinker in exchange.
Choose your username
This will be the address for your site.
yourname.floggy.xyz
Letters, numbers, and hyphens only
The editor, the dashboard and the live blog, with nothing for you to keep running.
Side by side, on the parts that take your time
With Self-hosted
- Getting startedProvision a host, install, wire DNS and TLS.
- Updates and securityYour job, on your schedule.
- NewsletterA separate service to add and keep running.
- AnalyticsAdd a tool, or add a tracker.
- Publishing from codeWhatever the stack you picked supports.
- Changing the designEdit templates, then rebuild and redeploy.
- LeavingYou already hold the files.
With Floggy
Recommended- Getting startedSign up, pick an address, publish the first post.
- Updates and securityHandled for you, continuously.
- NewsletterBuilt in. The subscriber list belongs to you.
- AnalyticsBuilt in, with no third-party trackers.
- Publishing from codeThe @floggy/cms SDK and the floggy CLI.
- Changing the designSwap themes from the dashboard.
- LeavingExport your posts and take the domain with you.
The honest tradeoff, in both directions
What you get
- Nothing to patch. The runtime, the certificate and the build stop being your problem.
- Newsletter, analytics and bookings sit next to the posts instead of being wired together.
- Themes swap from the dashboard, so changing the design is not a rebuild and a redeploy.
- Publish from the editor, the CLI or the API, whichever one you are already in.
What you give up
- Root access. No arbitrary plugins, and no code of your own running beside the blog.
- A stack you own has no plan gates on it, because there is no plan.
- A self-hosted site can be any framework you like. Here the rendering is ours.
- If you already run a server, a blog on it rides along on infrastructure you have.
What it costs to stop maintaining it
Start free on a subdomain. Go Pro for a custom domain, premium themes, and everything else.
Free
Everything you need to start writing in public.
Get started- Blog with posts on a floggy.xyz subdomain
- Free themes and layouts
- SEO, RSS, and sitemap built in
- Navigation builder and portfolio sections
- Co-authoring on shared posts
- Analytics for the last 7 days
Pro
1-week free trial$8.25/mo, billed yearly
The full platform, on a domain you own.
Get startedFree for a week. No card needed to start.
Everything in Free, plus:
- Custom domain and premium themes
- Notes, tasks, and calendar booking
- Newsletter: subscribers, broadcasts, custom sending domain
- Headless CMS: API, webhooks, SDK and CLI
- Hide your blog from Floggy
- Full all-time analytics
Common questions
Do I keep my domain?
Yes. You register and own the domain; Floggy is just what it points at. If you leave, you repoint it somewhere else and your readers follow. Nothing about the address depends on us staying in business.
Can I get my content out?
Yes. Posts are exportable, and the same headless API the site reads through is available to you: the @floggy/cms SDK and the floggy CLI can pull everything you have published into any site or script you like.
Is Floggy a headless CMS or a hosted blog?
Both, and you do not have to choose up front. Write and publish in the dashboard and Floggy hosts the blog for you, or read the same content through the SDK and CLI and render it in your own app.
Can I move an existing blog over?
Yes, though you move the posts yourself. Publish them here first, in the editor or through the CLI, check the result on your floggy.xyz address, and only repoint DNS once everything is in place. Readers then never land on a half-built site.
Start writing today
Claim an address, publish your first post, and keep the domain and the audience whatever you decide later.
Your own domain
Everything lives at an address you control.
Nothing to wire up
Publishing, audience and analytics ship together.
Reach inboxes
A newsletter and a subscriber list, built in.