"Our team was using five different tools and nobody could agree on which was the right place to look. SolidWiki set up a MediaWiki for us, and within two weeks everyone had stopped asking 'where is this?' in Slack. The training session was genuinely helpful - our non-technical people picked it up in an hour."
Stop Losing Work in
Scattered Docs &
Old Slack Threads
We set up MediaWiki for your team - a single, searchable knowledge base where nothing gets buried. We're a small, focused MediaWiki development company. Our first real client wiki is already live, and we're ready to build yours next.
A New Team With
One Clear Focus
We're not going to pretend we've been doing this for fifteen years. SolidWiki is a small, focused team that set up its first MediaWiki installation for a real client and saw firsthand how much difference a properly organised knowledge base makes to a growing team. We work exclusively with MediaWiki. We're transparent about where we are as a business, and we believe the best way to build a reputation is to do the actual work well - not to claim a history we don't have.
Your Team's Knowledge Is
Everywhere and Nowhere
It starts small. A shared Google Drive folder here, a Notion page there, some important context buried in a Slack thread from six months ago. Before long, nobody knows where to look, and new hires spend their first month just piecing things together.
This isn't really a productivity problem - it's a knowledge problem. The longer it goes unaddressed, the more it costs you in lost time, slower onboarding, and people walking out the door with knowledge that only existed in their heads, rather than anywhere searchable.
There is a straightforward fix for this.
A proper wiki - built right, from day one. One place. Everything searchable. Your whole team knows where to look.Everything Your Wiki Needs,
Done Properly the First Time
MediaWiki is all we do. So when you work with us, you get someone who has thought carefully about how to set it up well - not someone reading the documentation for the first time on your project.
MediaWiki Setup & Server Configuration
Full installation on your VPS or dedicated server - MediaWiki core, SSL certificate, firewall rules, Redis caching, automated daily backups, and proper admin documentation handed over from day one.
Wiki Design, Skin & Branding
A custom MediaWiki skin built around your brand - your logo, your colours, your typography - designed to work cleanly on both desktop and mobile, with single sign-on available if your team needs it.
Content Migration to MediaWiki
We move your existing content into MediaWiki from wherever it currently lives - Confluence, Notion, SharePoint, or elsewhere - converting it carefully so formatting, links, and structure all carry over intact.
Ongoing Support & Maintenance
Once your wiki is live, we keep it that way - core and extension updates, ongoing backups, uptime monitoring, and a quick response if anything ever needs attention.
Simple Process, No Grey Areas
You'll always know what's happening, what comes next, and when. We designed our process this way because we've all experienced the frustration of not knowing where a project stands.
We Have a Quick Call First
Before recommending anything, we want to understand your situation. Free, thirty minutes, no pressure to continue.
You Get a Written Proposal Within 48 Hours
Every deliverable listed, fixed price, realistic timeline. Nothing hidden. Commit only when satisfied.
We Build in Short Sprints and Show You Progress
Weekly sprints, you review each one. Nothing moves forward until you're happy. No surprise reveals.
We Launch Together and Train Your Team
Go live together, team training included, admin documentation handed over, and thirty days of post-launch availability if anything comes up.
Why Work With Us,
a Team Just Getting Started?
Honest answer: we can't offer ten years of history. What we can offer is focus, care, transparent pricing, and a genuine commitment to doing the work properly.
What Our First Clients
Actually Said
We've completed one client wiki setup so far. These are the real people we worked with and exactly what they told us.
"The fixed-price proposal laid everything out clearly - what they'd deliver, when, and for exactly how much. They kept to it. What really surprised me was that our HR coordinator, who has no technical background, can now create and update wiki pages without any help."
"What I appreciated most was the honesty. Before we agreed to anything, they told me clearly what MediaWiki is good at and where it has limitations for our use case. The wiki they set up is clean, loads fast, and - importantly - the team actually uses it. No forced adoption needed."
Questions People Ask
Before They Reach Out
Honest answers to the things people actually want to know before committing to a wiki project with a new team.
A basic setup typically takes about a week. A full project - including custom branding, content migration, and team training - usually takes two to four weeks depending on how much existing content needs to move over and how much customisation you want.
No. Once your wiki is set up with a visual editor enabled, creating and editing pages works similarly to using a basic word processor. Several of our clients' least technical team members are now their most active wiki editors.
Yes. Migrating content from Confluence, Notion, SharePoint, or similar platforms is one of our core services. We convert your existing pages, preserve formatting and links wherever possible, and validate everything after the move so nothing is lost or broken.
You do, completely. Your wiki runs on your own server using open-source MediaWiki software. There's no proprietary lock-in, no dependency on us to keep it running, and no recurring licence fee.
Ongoing support covers core and extension updates, regular backups, uptime monitoring, and quick fixes if something goes wrong. Plans start from $100 per month, scaled to the size and complexity of your wiki.
MediaWiki is open-source and self-hosted, meaning there are no per-user fees and your data lives on your own server rather than a third party's cloud platform. Notion and Confluence are easier to start with out of the box, but their costs grow with your team size, and you don't have the same level of control over where your data lives.
Yes. Every wiki we build includes SSL encryption, firewall configuration, access controls, and automated daily backups as standard - not as an optional upgrade. We also configure user permissions so only the right people can see or edit specific content.
That's a fair question, and we'd rather you ask it directly than wonder about it quietly. We don't have ten years of history, but we have deep, exclusive focus on MediaWiki, a transparent fixed-price process, and real client feedback you can read above. We're also happy to show you a working example before you decide anything.
Yes. We're glad to walk you through a live example during your free initial call, so you can see exactly what a properly configured MediaWiki installation looks and feels like before committing to anything.
Either works. If you already have server infrastructure, we'll set MediaWiki up on it. If you don't, we can recommend and configure suitable hosting as part of the setup process.
Tell Us About
Your Project
Fill in the form and we'll reply within 24 business hours. No commitment, no sales call unless you want one.