Built by developers, for game devs
Nectory started as a side project to solve a real problem: writing good documentation for a Minecraft plugin and having nowhere decent to put it.
The story
Every Minecraft plugin developer knows the problem. You've built something great, but your documentation lives in a messy forum post, a GitHub README nobody reads, or a wiki platform that looks like it was designed in 2008. Your users can't find what they need, and you spend half your time answering the same questions in Discord.
Nectory was built to fix that. We wanted a platform that's clean enough that you're proud to send people to it, powerful enough to handle real documentation needs, and simple enough that you'll actually keep it up to date.
We started with Minecraft plugins, but the same problem exists everywhere in the game dev world — Roblox game creators, modding teams, server owners, community wikis. Anywhere people are making things for other people to use, there's a documentation problem we can solve.
What we believe
The principles that guide every decision we make on Nectory.
Docs should be beautiful
Good documentation is one of the most valuable things a developer can ship. It deserves a platform that treats it that way — not a wiki engine from 2009.
Speed matters
A docs site that takes 3 seconds to load is a docs site nobody reads. Every page in Nectory is statically rendered and edge-cached worldwide.
Built for communities
Game developers don't write docs for enterprises — they write for players, modders, and contributors. Nectory is built with that audience in mind.
Simple by default
Most wiki platforms are powerful and bewildering. We'd rather ship something that works brilliantly for 90% of use cases than bury you in config.
Come build something with us
Nectory is in active development. We ship fast, listen to feedback, and care about every docs site on the platform.