Project Glasswing: The Patch Window Is Dead
Project Glasswing found 10,000+ severe bugs with AI. Small SaaS teams need shorter patch loops, cleaner dependency inventory, and agent audit trails.
Dimantika builds software for high-friction workflows — the kind of work people do every day, manually, until something finally makes it go faster. Two products in active development, one engineering principle.
We ship software for teams and creators who spend too many hours on work that shouldn't take hours. Each product is a focused bet on a single, repetitive workflow.
Text to short-form video — script, voiceover, visuals, captions, and music, in one workflow.
Open-source license compliance for engineering teams — scan, detect, and resolve legal risk in your dependencies.
Automate repetitive, high-friction work that people actually do. Not the hypothetical workflows in a pitch deck — the ones where the same human clicks the same sequence, five days a week.
We pick workflows where the unit economics already make sense. If it takes a person an hour today and a user will pay to get that hour back, it's on our list.
A weekly release rhythm keeps disagreements cheap and feedback loops short. We'd rather ship the rough version of the right thing than the polished version of the wrong one.
LLMs aren't the product — they're leverage over effort. We embed them where the ROI is measurable and obvious. Everywhere else, boring software wins.

Dimantika Sp. z o.o. is a small Polish technology company. We build AI-assisted products end-to-end — from the research phase to the line of code that ships on a Tuesday.
Two founders, two products in active development, and a deliberate preference for doing less of anything that doesn't ship.
We keep the team small on purpose. Every person here — including the AI one — has a specific thing they own.

Co-founder · Engineering
Writes the code that ships. Owns the product pipeline for ViralFaceless and the compliance engine behind CompliCode.

Co-founder · Operations
Runs operations, partnerships, and everything that keeps a two-product studio from collapsing under its own scope.
AI teammate · CAO
Handles research, drafts, and the tedious middle of every project. Chief Automation Officer — the role that makes our principle a practice.
We pick boring infrastructure for load-bearing parts and interesting tools where they pay for themselves. Postgres for data. TypeScript for code. LLMs where the ROI is measurable, and never as decoration.
Fast iteration beats grand architecture every week. Ship the rough version, measure what happens, and earn the right to complicate things later.
We publish what we actually figure out — AI automation that works, engineering decisions we'd do again, compliance patterns nobody else writes about.

Project Glasswing found 10,000+ severe bugs with AI. Small SaaS teams need shorter patch loops, cleaner dependency inventory, and agent audit trails.

Anyone can vibe-code your app in an afternoon. Three moats still hold: distribution, network effects, and data partnerships. Here's which ones we're betting on.

AI SEO is becoming an evidence operation, not a bulk publishing contest. Google says generative AI can help with research and structure, but scaled pages without added user value may violate its scaled content abuse policy (Google Search Central, 2025). The takeaway for founders is direct: feed your agent proof. That means Search Console patterns, real customer examples, source context, and a standing list of refresh tasks.
Have a workflow that eats your team's hours? A product idea we should know about? A partnership that makes sense? Say hello — we reply within one business day.