When I started StreamCraft, the idea was fairly simple.
A streamer can produce hours of content in a single evening. Yet once the live ends, most of that content disappears almost immediately into a VOD.
Not because there's nothing interesting in it.
But because you have to rewatch it, find the good moments, decide which ones are worth posting, edit them, put them in the right format, add captions, export, then post.
And when you stream regularly, it starts again a few days later.
I wanted to shorten the distance between having created something live and actually being able to share it elsewhere.
That's how StreamCraft was born.
Today, an important chapter of that story ends.
StreamCraft is leaving beta.
And with that, StreamCraft becomes:
Apogia.
Why Apogia?
StreamCraft was a good name to start with.
It described fairly directly what I was building: a tool around streaming and content creation.
But over the months, I understood that the problem I wanted to solve was broader than just "making Twitch clips".
The real problem is everything that happens between creating long-form content and turning it into something you can actually use and post.
Spotting the interesting moments.
Understanding what happened.
Choosing.
Adapting.
Editing.
Posting.
And, eventually, understanding the creator well enough to help them through that whole process without making the creative decisions for them.
That's the vision Apogia now stands for.
Apogia succeeds StreamCraft with its own identity and its own domain, apogia.app.
The project stays the same. Accounts stay the same. The work done during the beta doesn't disappear.
But the name changes because the product's ambition changed.
Where does Voskya fit in?
Apogia is also the first product built under another new identity: Voskya.
The two names don't play the same role.
Apogia is the product.
It's the brand you'll see when you import a VOD, look for a moment in a stream, or get a clip ready to post.
Voskya is the company behind the product.
It exists so Apogia can be built today, and potentially other products tomorrow.
So the signature is simply:
Apogia by Voskya.
I care about that separation for a fairly simple reason: a product should be able to be loved for what it is, independently of the company building it.
What the beta taught me
The StreamCraft beta was obviously meant to find bugs and check whether the technology worked.
But looking back, that's not the most important thing it taught me.
Above all, it forced me to confront some of my assumptions with reality.
At first, I mostly imagined StreamCraft for streamers doing anywhere from a few dozen to a few thousand viewers.
The people who actually came and used the product were often different.
Smaller creators.
Hobbyists.
Streamers with a few dozen viewers who had been streaming regularly, sometimes for years.
It would have been easy to treat that as just an acquisition problem.
I ended up understanding it was mostly information.
The size of a Twitch channel doesn't necessarily tell you whether someone needs Apogia.
A creator with a small audience who streams regularly, piles up VODs and wants to grow their presence elsewhere can feel this problem far more than a much bigger creator who already has a team around them.
So the right question isn't only:
"How many viewers does this streamer have?"
But rather:
"Are they regularly creating content they'd like to make more of?"
A successful generation is not a success
I also learned something slightly more uncomfortable.
Making the technology work isn't enough.
Apogia can analyse a VOD correctly.
It can find good moments.
It can produce nice clips.
And despite all that, create no value at all if nobody posts them.
So the real loop isn't:
VOD → successful generation.
It looks more like:
VOD → moment recognised → clip chosen → posted → next VOD.
That's the behaviour I now want to optimise for.
Not the number of buttons.
Not the number of features.
Not the number of clips the system can put out.
The outcome that counts is a creator finding something they genuinely want to post.
Early users pushed the product much further than expected
Some of you also used StreamCraft in ways I probably couldn't have reproduced myself in internal testing.
One user analysed 23 VODs and put out 92 clips, simply to push the product and try to find where it broke.
His feedback, after that heavy use, was that he was still looking for flaws and so far only saw positives.
That kind of usage is worth far more to me than a demo that works perfectly once.
It's also thanks to those users that I can now consider StreamCraft ready to leave beta.
What will not change
The name changes.
The product will keep changing a lot.
But some principles shouldn't.
Technology should reduce the work, not replace the creator
Apogia can analyse.
Apogia can suggest.
Apogia can prepare.
Apogia can speed things up.
But the final decision has to stay with the person creating the content.
I don't want to build a machine that automatically decides what a creator should find funny, important or interesting.
I want to build a machine that can tell them:
"Here's what I found. Now it's your call."
That difference may look small.
To me, it's fundamental.
Why leave beta now?
Leaving beta doesn't mean Apogia is finished.
It probably never will be.
There will still be bugs.
Situations we've never run into.
VODs the system gets wrong.
Features to improve.
And certainly a few ideas I think are excellent today and will laugh at a year from now.
Leaving beta means something else:
the core of the product works well enough that I can now honestly offer it as a real product, with a clear promise, clear limits and a clear price.
It also means starting to answer a question the free beta couldn't settle:
does what we're building create enough value for someone to accept paying for it?
I consider that question just as important as the technical ones.
Because Apogia can only keep existing and improving if it becomes a sustainable product.
For those who were here during the beta
Still, I want the people who agreed to use StreamCraft while it was still experimental to have a particular place in this transition.
You tested imperfect versions.
You waited on some analyses.
You found bugs.
You sometimes explained to me why a feature I thought was obvious really wasn't.
And above all, you let me observe what happens when someone actually uses the product, rather than imagining what they might do with it.
Concretely: if your account was created before 15 August 2026, you keep your plan at half price for 12 months. The Founders offer is closed to new signups, but it stays yours. Just join the Discord server and run /link there to attach your account, and the discount applies automatically when you pick your plan. There's no deadline to link your Discord.
This offer isn't a way to make you pay a debt to the project.
It's simply a way to recognise that you were here before Apogia was really a commercial product.
Thank you.
What Apogia wants to become
Today, Apogia starts with a fairly precise problem:
turning hours of long-form content into editorial opportunities you can actually use.
But I don't think the story stops at clipping.
Over time, Apogia can become a layer of intelligence between a creator's content, their identity, and the places they want to post.
A system that understands more of what happened across hours of content.
That finds moments again.
That connects them.
That makes transforming them easier.
That prepares different versions.
And that helps several creators when they make something together.
All of it with one constant rule:
Apogia should help the creator make better decisions, not make those decisions for them.
What's next?
This launch doesn't really feel like a finish line.
It feels more like the moment I finally take the training wheels off the bike.
During the beta, a lot of decisions could still be justified with:
"We'll see once the product launches."
That answer doesn't really exist from today on.
Now I have to find out who actually gets value out of Apogia.
Support them.
Watch what they post.
Understand why they come back, or why they don't.
Keep improving the quality of the moments we surface.
And progressively build what comes next without losing sight of the original problem.
Thank you
Apogia could have stayed a personal project for a long time, one I kept piling new things onto.
The beta gave it something far more valuable:
real users.
People who imported their own streams.
Who tried the results.
Who broke some of my assumptions.
Who confirmed others.
And who helped me understand a little better what this product could become.
StreamCraft was the name this experiment started under.
Today, that experiment becomes a product.
Welcome to Apogia.
Thank you for being here at the start.
Mathias Founder, Apogia
Apogia by Voskya