๏ปฟ
๐ฑ It started with a package
Before Dock had a name, a website, or a public Discord bot, I was working on packages for ER:LC design servers. A package is basically code a user can buy from a server and use for their own community. One of the things I wanted to make was a design bot package with a custom Roblox verification system, and that meant the bot needed an API.
I could have made every buyer host the API themselves, but that would immediately make the package harder to use. Some people do not know how to host an API, some do not want to pay for another server, and some do not want to buy and configure a domain just for one bot. So I decided I would host the API myself and separate each customer's data on my side. At the time, that was the whole idea. There was no plan for a public verification platform.
๐ The website that was not supposed to exist
After about a week of building the API and finally getting it hosted, I ran into a very obvious problem: people needed a way to actually access it. They needed an API key, that key needed to be connected to the right Discord server, and I needed some way to manage the data behind it.
So I made a website. It was quick and simple because the website was not meant to be a product by itself. Its job was basically to let someone connect their server, create an API key, and start using the API. That tiny website and API are what eventually became the first version of Dock.
โต Turning it into Dock
After roughly another week of people using it, I started to realize the service had more potential than something bundled with one package. It already solved a useful problem, people were actually engaging with it, and there was no real reason it had to stay tied to the original design bot.
That is when I decided to make it public and came up with the name Dock. There is not a deep hidden meaning behind the name. I wanted something clean, minimal, easy to remember, and not already used by a bunch of Discord bots. I liked Dock, so that became the name.
๐ My first public bot
Dock was my first public Discord bot, so I genuinely did not know what to expect after releasing it. I was not running paid ads, doing some huge creator campaign, or trying to force growth. Most of the growth came from people finding Dock, using it, and inviting it to another server.
That is why the early growth surprised me as much as it did. Around six months after the public release, Dock reached roughly 1,000 Discord servers. Then, only about four months later, it reached 2,000. The second thousand arrived much faster than the first, even while I was spending a lot of my time rebuilding the product in the background.
๐ The project changed faster than the codebase
The weird part about that growth is that the original Dock was never architected for what it became. The first API was built because one package needed it. The first website was built because users needed API keys. Then verification was added, server configuration grew, premium plans appeared, more developers started using the API, logs became important, security became more complicated, and the dashboard kept expanding.
Every addition made sense on its own, but eventually the product had outgrown the assumptions of the original project. Dock was no longer a small API with a website attached to it. It had become a developer platform and a server management/verification bot that thousands of communities were relying on.
๐ ๏ธ Why I rebuilt it
By early 2026, I reached the point where I did not want to keep layering major systems on top of the first version. In March, I started what became Dock V2. The plan grew quickly: the dashboard was rebuilt, the API was rewritten, billing and entitlements changed, verification was reworked, native Alt Detection was built, Account Standing and moderation became structured systems, and a lot of the infrastructure underneath everything changed too.
That rewrite took around six months. I am still a solo developer, so it was a lot to do at once, but it also gave me the chance to build Dock around what the product actually is now instead of what I thought I needed during that first week.
โค๏ธ Looking back
The part I like most about Dock's history is that none of this was planned in some perfect roadmap from day one. One problem led to another. The package needed an API, the API needed keys, the keys needed a website, people started using the website, and that made me realize the service could stand on its own.
I never expected a small API I made for myself to turn into something used by thousands of Discord servers, especially without really advertising it. I also do not know exactly how far Dock will go from here. What I do know is that V2 finally gives it a foundation built for the project it became, and I want to keep improving it with smaller, more consistent releases instead of waiting for everything to turn into another giant rewrite.
Thanks for being part of Dock. Whether you found it when it was tiny or joined after thousands of servers already had it, you are part of a project that started almost by accident.