ship first, polish later
code on a laptop helps nobody. we push to production as soon as a feature is useful, then iterate based on what real users do, not what we imagined they’d do.
the studio
a small studio that writes its own software.
vøiddo is six engineers, one founder, no investors, and one rented vps in a frankfurt datacentre. we ship ai tools, browser extensions, wordpress plugins, dev utilities, and a small library of browser games. we do not pitch, we do not waitlist, we do not gate the free tier behind a credit card.
how we started
the studio started in 2024 because the founder had a side project on shopify and ran out of patience for writing product descriptions by hand. the obvious shortcuts did not work — generic ai writers produced copy that sounded like every other dropshipping store, and the dedicated “ai listing tools” were either built for amazon-only or priced for a six-figure marketing budget.
egor michurin wrote the first version of scrb over a long weekend in tel aviv: one fastapi process, a postgres table, a brittle wrapper around an llm api, no front-end. it was ugly, but it shaved hours off a real workflow. that was the test. if it saves us time, it’s probably worth shipping. if it does not, it’s a hobby project and we move on.
between 2024 and 2026 the studio went from one script to a small portfolio: scrb (web app, chrome / firefox / edge extensions, wordpress plugin), rankd (a second flagship — ai culture judge), and tells (the third flagship — text-first ai for reading what people don’t say out loud, live on paddle since may 2026). on the side: roughly thirty free dev utilities, eleven browser extensions, eight browser games, twenty-seven npm packages, and two wordpress plugins in the official directory. the team grew from one person to six. the operating philosophy stayed the same.
we said no to venture capital from the first conversation. outside money buys outside timelines and outside priorities. bootstrapping is slower, but it leaves the question “what should we ship next?” entirely up to us. so far that trade has been worth it.
what we ship
three flagships do most of the talking. scrb writes ai product descriptions for amazon, etsy, shopify, and woocommerce sellers — paste a photo or a link, get listing copy that doesn’t smell of chatgpt, in twenty-five languages. it is live as a web app at scrb.voiddo.com, as a chrome / firefox / edge extension, and as a free wordpress plugin in the official directory.
rankd is the ai culture judge — name a film, a game, a book, a song, get a letter grade, a numeric score, and one short opinion in four seconds. no fence-sitting, no plot summary, no “it depends on what you like.” it lives at rankd.voiddo.com and as a chrome extension.
tells is the third flagship. it reads the things people don’t say in plain text — read a message, read a person, read a profile. v1 went live on paddle in may 2026; free tier 5 / month, starter $14.99, pro $34.99, forensic $79.99. you can open it at tells.voiddo.com if that sentence made any sense to you.
around the flagships are the supporting tools. roughly thirty free dev utilities at tools.voiddo.com — regex testers, json formatters, jwt decoders, the kind of things that should have always been one click away. ten or so paid browser extensions, eight browser games at games.voiddo.com for people who can’t stand modern free-to-play, and twenty-seven npm packages under the @v0idd0 scope. nothing in the catalogue exists because someone told us it would “rank well” — every product is something at least one of us actively uses.
core beliefs
the actual rules we use when we disagree about what to do next.
logs over opinions
most product debates die quietly when somebody actually reads the server logs. we look at error rates, request volumes, conversion funnels. the data settles the argument faster than we can.
lean is a feature
six people and a lot of automation is how we punch above our weight class. small team forces small meetings, sharp scope, and aggressive defaults. we stay this size on purpose.
small diffs, fast rollback
we deploy multiple times a day in changes you can read in one sitting. when something breaks — and it does — rollback is one button, not a postmortem-shaped meeting.
honest about limits
we’d rather lose the sale than oversell the tool. if scrb is wrong for your workflow, the support email will tell you so and recommend a competitor. people remember who didn’t lie to them.
boring infra, weird products
we use boring, well-understood tech — postgres, redis, fastapi, nginx, paddle. the surprises are reserved for the products themselves, not for the 3am page-out.
against the grain
most of what passes for “ai-powered saas” in 2026 is the same playbook on a different homepage: a sign-up form that asks for a credit card to see the product, a free tier with a 1-of-5 watermark on every output, dark patterns around cancellation, and a series-a deck somewhere in the founder’s drive. the people writing this software are optimising for an exit, not for you.
we don’t do any of that. there is no credit card on the free tier of scrb. there is no usage cap on the free tier of rankd. cancellation lives one click deep in your account page, with no “are you sure” modal designed by behavioural economists. our pricing page is a pricing page, not a maze. we use paddle as merchant of record, which means taxes and refunds happen on the same day you ask, not in a support thread that takes nine business days.
none of this is a moral position. it’s the product working for the user instead of the user working for the product. it turns out a lot of people prefer it that way.
how we work
the team is six engineers across tel aviv, haifa, and one small place up north that one of us refuses to name on the internet. we work fully remote, ship daily, and meet once a month at a small pub in rishon lezion. by long-standing house rule we don’t talk about work at the pub — whoever brings up a jira ticket buys the next round. most of us break the rule before the second pint. the rule survives because the fines pay for the round.
asynchronous by default. we document everything in markdown, ship pull requests in english, review in english, and let the time zones work for us. when frankfurt is asleep, tel aviv is at lunch. when tel aviv is asleep, somebody’s usually awake enough to notice the alert.
the team page (/team/) has the full crew with portraits, bios, and the occasional anecdote about who shipped a hotfix from the bathroom of a wedding reception. we are not actively hiring full-time, but if you build interesting things and want to say hello, the contact form works.
technology
we pick boring tech on purpose. postgres for everything that has to be true tomorrow. redis for everything that can be wrong for thirty seconds. fastapi for the api surface, react for the front-ends that need it and vanilla js for the ones that don’t. nginx and systemd in front of all of it. paddle handles money, vat, and chargebacks. one vps, one operator on call, one rollback button.
TypeScriptPythonPostgreSQLRedisReactFastAPICeleryPaddleNginx
a more honest breakdown lives at /studio/#stack — including which editor we actually use and which ai model we won’t name in public.
where we are
vøiddo is legally registered in israel. the team is fully remote. payments and tax compliance run through paddle (ireland, merchant of record), so customers in eighty-something countries get a local-currency receipt without us touching a single tax form. uptime is monitored from frankfurt, london, and singapore.
get in touch
there’s no support queue with a fifteen-business-day reply target. write to hi@voiddo.com and a human reads it the same day. for press, brand kit, or factsheet, the same address works.