We set up MediaWiki for your team — a single, searchable knowledge base where nothing gets buried. Small focused team, first real client wiki done. Ready to build yours.
We're not going to pretend we've been doing this for 15 years. SolidWiki is a small, focused team that set up its first MediaWiki for a real client and saw how much of a difference a properly organised knowledge base makes. 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.
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 people spend their first month just piecing things together.
This isn't a productivity problem — it's a knowledge problem. The longer it goes unfixed, the more it costs you in lost time, slower onboarding, and people leaving with knowledge 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.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 docs for the first time on your project.
Full installation on your VPS or dedicated server — MediaWiki, SSL, firewall rules, Redis caching, automated daily backups, and proper admin documentation from day one.
Custom skins that match your brand, SSO integrations, extension setup, user roles, and full mobile responsive design — so your team actually wants to use it.
We move everything from Confluence, Notion, Google Docs, or SharePoint — preserving your page structure, formatting, and internal links. Zero data loss, properly structured.
Monthly plans covering daily backups, core updates when they release, security patches, uptime monitoring, and priority response when something needs attention.
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.
Before recommending anything, we want to understand your situation. Free, 30 minutes, no pressure to continue.
Every deliverable listed, fixed price, realistic timeline. Nothing hidden. Commit only when satisfied.
Weekly sprints, you review each one. Nothing moves forward until you're happy. No surprise reveals.
Go live together, team training, admin docs handed over, 30 days post-launch availability.
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.
We've completed one client wiki setup so far. These are the real people we worked with and exactly what they told us.
"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."
"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."
Honest answers to the things people actually want to know before committing to a wiki project with a new team.
A basic setup — MediaWiki installed, configured, secured, with a custom skin and your team trained — typically takes 2 to 4 weeks from the day we start. If you also need migration from another platform, or if the design is complex, that can extend to 4 to 8 weeks. We give you a specific date in the proposal before you commit.
No. MediaWiki's editing interface is designed for normal people — the same platform powers Wikipedia and has millions of non-technical editors. We also include a hands-on training session with every project so your team learns how to create pages, edit content, and organise articles by themselves.
Yes. We migrate content from Confluence, Notion, WordPress, Google Docs, and SharePoint. We don't just export and dump — we structure the migration carefully so your content hierarchy and internal links make sense on the other side. Zero data loss is our technical standard. We verify content after migration before calling it done.
You do — completely and permanently. Every file, every database record, every configuration file lives on your server and belongs to you. MediaWiki is open source software. You can stop working with us and manage it yourself, or hire someone else entirely. No lock-in and no ongoing dependency on SolidWiki to keep your wiki running.
Our monthly support plans start at $500/month and cover daily automated backups with 30-day retention, MediaWiki core and extension updates, security patches, uptime monitoring with alerts, and priority response if something needs fixing. You also get a short monthly summary so you always know what's been maintained.
Notion and Confluence are SaaS products — you pay monthly per user, the company controls the software and your data. MediaWiki is open source. You install it on your own server, you own everything, and there are no monthly per-seat fees. It scales from 10 articles to 10 million. The trade-off is that it needs proper setup and maintenance, which is what we handle.
Yes, when set up properly — which is exactly what we do. Every setup includes SSL, firewall configuration, access controls, spam protection, and automated daily backups. You can restrict the wiki to your team only, control who can view which sections, and manage user permissions by role. Security is part of every build.
That's a completely fair question. We're new and we say so openly. We've completed one real client wiki setup and those three people are happy with the result — you can read what they said above. We offer focus on one thing, transparent pricing in writing before you commit, weekly progress updates, and honest communication throughout.
Yes. If you'd like to see a real MediaWiki setup before committing to anything, tell us in the contact form and we'll arrange a walkthrough on a call. We'll show you how it actually works from a user's perspective and what a setup for your situation would look like specifically.
Either works. If you already have a VPS you want to use, we set everything up there. If you don't, we'll tell you exactly what to provision and from where — or we can handle the server setup as part of the project. We'll recommend the right size based on your team without over-specifying something you don't need.
Fill in the form and we'll reply within 24 business hours. No commitment, no sales call unless you want one.