It s a proof-based external vulnerability scanner for startups, SaaS teams, fintech products, and lean technical teams.
The problem I m trying to solve is simple:
Most small teams ship fast, but they don t always know what their external attack surface looks like. Traditional scanners often return long noisy lists, but not enough clear proof, context, or business impact.
Interactive stories have existed for years - but creating them still feels unnecessarily complicated.
Writers often need one tool to write, another to manage branching paths, another to publish, and somewhere else entirely to find readers and monetize their work.
As readers, we also felt that interactive stories were scattered across different apps, games, websites, and communities.
That s one of the reasons we started building Forgeon.
We ve been thinking a lot about what actually makes a creative tool worth learning.
With Forgeon, we re building an editor where writers can create branching stories visually - connecting scenes, adding choices, multiple paths and endings, RPG mechanics, relationships, music, illustrations, and other interactive elements.
But adding more features doesn t necessarily make a better creative tool.
For us, the goal is to make something powerful enough for complex interactive worlds, while still being approachable for someone who just wants to tell a great story.
I'm DOCL. By day I'm a steel fabricator. No CS degree, no tech background, just hobby-level skills and a curious mind for how things work. Everything I know about building software I taught myself at night and on weekends, around a full-time trade job.
Our team has been spending a lot of time thinking about existing products rather than brand-new ones.
One thing we've noticed is that as a product grows, knowledge becomes fragmented. Some decisions live in documentation, some in Git history, and some only in the minds of the people who built the feature months ago.
Adding a "small feature" often means spending more time understanding the existing system than actually implementing the change.
That's exactly the problem we wanted to tackle with the new Brownfield workflow in MySpec.
Yesterday was my 27th birthday. Instead of the usual dinner, I spent the morning in VIM (btw) shipping the waitlist for Squad In Sync.
The context: I was trying to plan my own birthday and NYE with my friends. Within 48 hours, the WhatsApp thread was 400+ messages deep. The flight info was buried, the restaurant link was lost, and half the group was in "decision paralysis" because they couldn't see the full plan.