Skip to content

Личный блог

What Happens Behind the Scenes at RobinSystem

The Tenth Month of Solo Development: On the Dream of Streaming, Mistakes, and Trust. I’ll talk about RobinStudio, the new pricing, and the future of RobinSystem.

robinsystem-behind-the-scenes-october-2026

Hi. Today is October 15, 2026, and I’d like to take a break from updates for a moment to share what’s happening behind the scenes at RobinSystem.

My username is Derick. I’m the sole owner and developer of this project. One person is responsible for the bot, overlays, settings, design, and support responses. Usually, you see the result of this work. Today, I want to talk about the work itself—including the parts that aren’t easy.

01How It All Began

As a kid, I was bursting with ideas for YouTube and livestreams. Back then, it was all about Minecraft: I wanted to film, go live, and create something of my own. My parents, like many others, insisted that I focus on my studies. In the end, the streaming didn’t work out. But my interest in it never went away.

Now, I want people who’ve decided to get started to spend less time searching for tools and figuring out settings. I know how easily you can get carried away by the very idea of streaming. And I want the technical side of things to help make that happen.

When I watched other people’s streams, I found myself paying more and more attention to what the streamers were using.

On a single channel, there could be five or six bots running at the same time. Each had its own commands, responses, and settings. The overlays also often looked as if they’d been pieced together from different sets. Individually, everything might have been convenient, but putting it all together into a cohesive stream wasn’t easy.

I wanted to create a system where the bot and the visuals worked in harmony—so that streamers could more easily navigate the settings, and what was happening in the chat and on screen would feel like part of a single broadcast.

That’s how RobinSystem began. At first, it was just an interesting experiment: would I be able to put it all together, and would anyone actually use it?

I started asking people to test the project. And one day, I heard:

“Wow, this is cool and convenient. I’m turning off all my old bots.”

For someone who had simply been testing an idea up until that point, those words meant a lot. At some point, you realize: what you’re doing has already been useful to someone else. I wanted to bring the project to fruition.

02The Tenth Month of Development

From then on, I began searching for like-minded people and those willing to support the idea. New users, suggestions, bugs, and new challenges emerged. The project began to grow much faster than I had expected.

During this time, the systems, overlays, and design were rewritten from scratch several times. Some things stopped working as the project grew, some needed to be made clearer, and some solutions simply turned out to be unsuccessful. Not every such overhaul is visible from the outside, even though it sometimes takes more time than developing a new feature.

RobinSystem now has dozens of modules and tools for streamers. And behind them are APIs, admin panels, and much more that most users never even see.

We’re now in our tenth month of development and support. Writing code, testing changes, figuring out someone else’s settings, answering questions, preparing posts—all of this still goes through me.

I try to respond to everyone and understand the situation of each specific channel. Sometimes it’s quick, sometimes it takes time. And yes, at times I get very tired. As the project grows, it’s becoming increasingly difficult to keep up with both developing it and maintaining what people are already using.

RobinSystem has given me a reason to grow. I’ve come to understand development better, learn more, and work much harder. Over time, I began to notice how this pace was taking a toll on my health. I truly regret that. You can’t buy your health later, even if you manage to finish everything you set out to do.

I enjoy this work. But I want to find a pace at which I can continue doing it without constantly compromising my well-being.

03When Things Go Wrong

The hardest days are when everything works on the test server, but under real-world load, it turns out differently. Testing on my own machine and the actual service that people are using at the same time sometimes show very different results.

There was a time when the service went down because of a mistake I made. After that, there was a lot of negative feedback. And I understand these people: someone has just set up the tool, is counting on it, and suddenly doesn’t understand why nothing is working.

People aren’t expected to know how much time I spent on this feature or how it performed in testing. They expect a service that works. That’s fair.

Situations like this are hard to deal with. Still, it’s up to me to take responsibility for my mistake and fix it. When I say I’m working on the project alone, I want to honestly explain how it’s set up. The responsibility for its operation still rests with me.

04Why I’m Still Working Alone

I wasn’t able to align expectations with everyone who got involved with the project. Some saw it primarily as a business and expected business-oriented decisions. I kept looking for the time and money to finish tasks and release them. There were also situations where I encountered deception. That’s part of the experience too, though it’s unpleasant to talk about.

Right now, I don’t have the means to hire more developers. But there’s also a personal challenge I want to address directly: I find it very hard to imagine handing over the source code to someone else. For ten months, I’ve been doing what I love every single day. Over this time, the project has become so much a part of me that the thought of sharing this responsibility is scary.

I’m also particularly concerned about user data and trust. RobinSystem is already trusted by streamers, including those with a verified badge on Twitch. This means a great deal to me. Behind every connected channel is a person who decided to use what I’ve built. I really don’t want to lose that trust.

I keep working because I enjoy what I do. I listen to my audience, go back to the tasks at hand, and try to gradually see them through to completion. Though not everything works out, and not right away.

05RobinStudio

There’s another part of my work that hasn’t been discussed much yet. For the past three months, I’ve been gradually developing RobinStudio—a Windows app that will combine RobinSystem and OBS into a single workspace.

rstudio
rstudio

I want users to be able to select an overlay, customize it, and immediately add it to the desired OBS scene—without the usual hassle of copying a link, creating a browser source, pasting the address, adjusting the dimensions, and repeating the process for the next widget. The app will handle this for you.

The development already includes a live preview of overlays, a scene configuration wizard, and OBS controls: switching scenes, source visibility, going live, and recording. I’m putting all this together so that preparing for a stream takes less time and doesn’t require keeping dozens of separate steps in mind.

For me, RobinStudio is the project’s next big step. My goal is for a person to be able to figure out the setup in about ten minutes and go stream with peace of mind. We still have a ways to go to reach that level of convenience. But that’s exactly what I want to boil all these settings and actions down to.

I’m really passionate about this idea. I keep coming back to the question: can we make it even simpler? Remove an extra step, make the settings clearer, send the result directly to OBS. I want routine actions to take literally just a couple of clicks.

rstudio2
rstudio2

About the first RobinStudio builds

When will RobinStudio be released?

I can’t give an exact release date yet. When a version is ready for early testing, I’ll announce it separately.

Who will receive the first builds?

Ultra subscribers will receive the first RobinStudio builds.

06About Subscriptions in 2027

I didn’t expect this kind of response. At first, I didn’t have a grand business plan: I was just interested in development and wanted to create a user-friendly tool.

Affordability is still important to me. The Premium plan already includes TTS, additional overlay customization options, higher limits, and a reduced store commission. I want streamers to be able to try out more features without a large monthly expense.

But there’s a change I want to mention in advance: starting in 2027, prices for paid subscriptions will increase. The cost for 30 days will be as follows:

SubscriptionCurrentStarting in 2027
Premium199 ₽249 ₽
Ultra399 ₽499 ₽

This decision wasn’t an easy one for me. The funding will allow the project to continue and provide a small cushion, making it easier to plan our work with peace of mind. For me, it confirms that the tools we’ve created are useful enough for people to be willing to pay for them. I still have a lot to learn about managing this aspect of the project.

I understand that everyone has their own budget. That’s why I’m announcing this change now, a few months before the new year. I really hope for your understanding.

Promo Code OCTOBER and Long-Term Discounts

Through October 31, 2026, you can activate the promo code OCTOBER to get a discount on your subscription. The terms and final price will be displayed in your account.

Long-term discounts are already available for Ultra:

  • 3 months — 5%.
  • 6 months — 8%.
  • 1 year — 12%.

I feel more confident in development than in marketing and business. While I’m still learning these aspects, I want to keep the service affordable while also giving myself the opportunity to develop it further.

07Things I Might Overlook

There’s one thing I’d especially like to ask for.

When someone encounters an error, they don’t always report it. They might work around the problem, put off configuring it, or simply leave. This is understandable: you came here to prepare for a live stream, not to figure out someone else’s code.

But from my perspective, this silence might make it seem like everything is working fine. I might not realize for a long time that some minor issue is preventing you from using the service every day.

If you notice a problem

If something isn’t working or seems inconvenient, please report it to support on the website. To start, just briefly describe:

  • What you clicked or tried to do.
  • What result you expected.
  • What actually happened.

A screenshot would also be helpful if it’s easy for you to attach one.

Your general feedback is important to me too: what features you use, which ones you’ve stopped using, and which settings took you a long time to find. These messages help me better understand where to focus my time.

I take full responsibility for the quality. But your outside perspective helps me notice things I might miss when I’m working on the same product every day.

08What’s Next

In October, I plan to launch a referral program for everyone and remove the pre-registration requirement. I want it to be easier for people who like RobinSystem to invite other streamers. I’ll share more details about the launch and terms separately.

I also need to focus more on promoting the project, creating content, and managing social media. That takes time, too—time I’m constantly short on between development and support.

I can’t even always say exactly what kind of support I’m missing right now. People, words, feedback? Honestly, I don’t know myself yet. But it’s important for me to hear from those who use the project: to understand where it helps and where it still gets in the way.

And a simple recommendation from someone who finds it convenient to use is very valuable right now.

If you’re thinking of a streamer you know

Perhaps there’s someone among your friends or colleagues who could benefit from RobinSystem. If you find it useful yourself, tell them about the project or send them a link to this post.

I’d be very happy to hear that someone found the tool they needed here thanks to your recommendation.

I want to keep working on RobinSystem. I still have a lot of ideas, and it’s important for me to understand which ones are truly needed by the people on the other side of the screen.

Thank you to everyone who’s already using the project, reporting issues, offering suggestions, and telling others about it. It means a lot to me that you’ve chosen RobinSystem and are giving me the chance to make it better.

Derick

Share this piece

Марк Дерик

Команда платформы