Sitepins hits 1,000 users this week.
It’s a small number in the world of SaaS, but it means something to us.
Sitepins started as a frustration. For years, we relied on Forestry CMS that worked beautifully across our themes, our websites, and the client sites we served at Themefisher, Gethugothemes, and Zeon Studio.
Then in 2023, it shut down. We were left supporting 100+ themes (now we have 200+ themes) with no good path forward. We tried every alternative back then. Nothing worked the way Forestry did. So we built our own.
Today, 1,000+ people use Sitepins to manage content on their Astro, Hugo, and Next.js websites. Teams use it. Solo developers use it. Freelancers managing client sites use it. They’re people who didn’t want to buy a massive CMS or fork over infrastructure costs. They just wanted a visual editor that works with their existing workflow.
Learning from the Early Days
The early users taught us what matters. They showed us that a CMS doesn’t need to be complex to be useful. They needed to:
- Edit content and images without rebuilding from the command line.
- Give clients access without handing them the keys to production.
- Use something that played nicely with static sites, not against them.
We listened. We kept it simple. We made it fast.
Building Sitepins has been about finding the gap between two worlds.
On one side, developers who love Git, version control, and simplicity. On the other, people who just want to edit content visually without knowing what a repository is. We built Sitepins in that gap.
A Milestone of Feedback
The weird thing about 1,000 users is it feels both huge and impossibly small. We know many of you by name. We read your feature requests. We see how you use the editor: what works, what breaks, and where you get stuck. That feedback has shaped everything we’ve built.
You made this real.
- To our first hundred users: Thank you. You took a chance on something unproven. You sent us bugs, feature ideas, and encouragement when we needed it most. Your names are still on our Discord, Internal Documents.
- To everyone who joined after: Thank you for believing in the vision. For integrating Sitepins into your workflows, recommending it to colleagues, and sticking with us through the rough edges.
What’s Next?
We aren’t slowing down. Sitepins was built specifically for static site generators like Astro, Hugo, and Next.js, and we’re focused on making it more useful for every workflow they power. We’re also learning that Sitepins fits into workflows we didn’t expect. Each of those use cases is teaching us something new about what Sitepins can be.
We’re also thinking beyond today’s web. AI and agentic workflows are changing how content is created and managed. We’re building Sitepins to be ready for that shift, so your content infrastructure works not just for you, but for the agents working alongside you.
This Is Just the Beginning
1,000 users tells us one thing clearly: we are solving a real problem. We haven’t cracked it perfectly yet. But we’re doing our best every day, and that’s worth celebrating.
If you’re reading this and you’re not yet a Sitepins user, we’d love to have you. Try it for free.
Thank you to everyone who got us here. Let’s build something even better from here.