six people. no office. no titles that matter.

writes the code, pays the server bills, replies to support email at 2am.

egor started vøiddo in 2024 after three years writing logistics-platform code at a fortune-500 company that nobody outside the company would ever see. the first scrb prototype shipped from a kitchen table in tel aviv at 2am on a tuesday because his then-partner asked, politely, whether the bedroom light could finally go off. it stayed on. the prototype shipped. the partner is now an ex-partner; the prototype is now a product. he still owns the backend architecture, the deploy pipeline, the postgres schema, the paddle integration, the email rails, the watchdogs that wake him up when something is on fire, and most of the other things nobody else wants to debug at 3am. writes go and python in roughly equal measure, occasionally typescript when ido is unavailable, sleeps less than the bedside therapist would recommend. owns the studio because nobody else wanted to own it.

once shipped a critical scrb hotfix at 2am from the bathroom of a wedding reception in caesarea. the bug was a stale cdn cache; the fix was a one-line invalidation; the laptop had three percent battery. nobody at the wedding noticed he was gone for nine minutes. his future ex-wife noticed.

"just deploy it and see what breaks."

makes the database queries run faster; calls your orm a war crime in writing.

dmitri spent ten years tuning postgres for payment and commerce systems — the kind of job where a forty-millisecond regression on a hot query is a conference call, and a thousand-millisecond regression is a resignation. he moved to estonia in 2023 for the residency programme and the weather, in that order, and now works from a third-floor flat in tallinn with a view of two cranes and the side of an apartment block. at vøiddo he owns the data layer end to end — the rankd ranking pipeline, the scrb usage analytics, the email-deliverability tables, and the postgres replicas that quietly survive when the primary catches fire at 3am. believes most performance problems are bad indexes, most bad indexes are bad orms, and most bad orms are written by people who never opened an `EXPLAIN ANALYZE` window. has been known to send unsolicited query review comments to other companies' open-source repos.

once spent four hours optimising a query that runs twice a year and saved the studio $0.83 in monthly compute. he framed the aws metering receipt and pinned it above his desk as a reminder that some optimisations are about principle, not money. somebody at a conference asked if the framed receipt was art; he said yes.

"your orm is hiding a terrible query."

makes the buttons actually work; rewrites the spacing scale when nobody asked.

ido grew up in a hungarian-speaking household in jerusalem with a grandmother who never quite forgave hungary, did a year in military intelligence learning that nothing is ever as urgent as someone tells you it is, then spent two years at a small design agency in budapest re-pixel-pushing menus for mid-tier hotel chains before tel aviv pulled him back in 2022. at vøiddo he owns the entire frontend surface — the scrb web app, the tells flagship, the rankd creator embeds, the admin dashboards we don't talk about publicly, and the marketing pages that show up on this very tab. mild opinions about accessibility (we use them anyway), strong opinions about bundle size (he will tell you), nuclear opinions about css-in-js (do not get him started). rewrites the design system whenever the spacing scale starts to bother him, which is more often than the rest of us would like and slightly less often than the design lead would like.

once redesigned the entire scrb settings page in budapest airport while waiting on a delayed connection. the redesign shipped from terminal 2, departure gate B14, on hotel-tier wifi. the connection itself never did. he flew home a day later and the new layout had been live for fourteen hours; nobody had filed a single bug. he still talks about that as the closest thing to a perfect deploy.

"we do not need another javascript framework."

keeps the lights on; treats vendor dashboards like a personal insult.

tal grew up in tel aviv and cut his teeth on security infrastructure for a mid-size fintech that, between 2019 and 2022, slowly became the kind of place where compliance memos started replacing engineering decisions. he walked out the morning his employer tried to push biometric tracking onto its own staff under the framing of "wellness." at vøiddo he runs everything we deploy — nginx configs, the rusted set of ci/cd pipelines, the monitoring stack that wakes him when scrb p95 drifts past a threshold, the systemd units that keep mailers, watchdogs, audit jobs, and rescue daemons coherent across a hetzner box that has been continuously online since february 2024. trusts bash scripts more than vendor dashboards because bash scripts have never silently changed pricing on him. has never met a yaml file he couldn't shorten. has been known to delete a 400-line helm chart and replace it with a 9-line shell script that survived a year longer than the chart did.

once fell asleep on the last train from tel aviv and woke up at the be'er sheva central station at four in the morning with no way back and a phone on three percent. spent the night on a bench arguing with a stray cat about whose station it was, paying for a sandwich at a 24-hour kiosk, and writing a postmortem about overnight train coverage on his phone in google docs. refuses to discuss the outcome of the argument with the cat.

"it works on my machine is not a deployment strategy."

maintains the visual language; will lose an afternoon to one comma in the wordmark.

roman studied industrial design in saint petersburg in a programme that still made students cut foamcore by hand, spent eight years inside agency rooms in moscow and then warsaw being asked to make the same kind of "bold disruptive" deck for a different bank every quarter, then moved to tartu in 2022 because the quieter rhythm made the work sharper and the agencies stopped sending briefs. at vøiddo he owns the visual identity end to end — the wordmark, the sigil, the typography, the product art direction, the stylised portraits you are currently reading alongside (yes, those are illustrations, no, there is no real photo of any of us on this page on purpose), the marketing pages, and the slow editorial system that keeps every public surface looking like it came from the same studio. still paints by hand on real paper before he digitises anything. still argues about kerning like it pays his rent (it does). still treats every public page as a trust surface rather than decoration and has been known to reject a banner because the gutter was three pixels off.

once kerned a single word in the wordmark four times in one afternoon. only the third version shipped; the other three he printed at home, framed at A5 size, and pinned above his desk as a reminder that almost-right is not right and that you will know the difference when you walk past the wall on the fourth morning. a visiting friend asked if it was concept art for a film. he said no, this is just kerning.

"make it darker."

breaks things intentionally; will file a bug against the bug tracker.

lev moved from saint petersburg to haifa as a teenager, studied applied mathematics at the technion because his mother thought "applied" sounded employable, and ended up in quality engineering almost by accident — a friend asked him to look at a flaky test suite over a weekend, the suite stopped flaking, the company offered him a job on monday, and he has never quite worked out how to leave the field since. at vøiddo he writes the playwright suites that run against every pull request, designs the fuzzers that feed malformed multipart data and weird unicode into the scrb and tells apis, runs the cross-language sweeps that check every public surface against ten translations, and maintains the test fixtures that let the rest of the team ship at 2am without breaking paying customers. keeps a running list of the worst bugs he has ever shipped pinned above his desk, including one he is still proud of from 2019 that caused a financial dashboard to briefly display every customer's balance as π.

once filed a bug report against the bug tracker itself. the bug report broke the bug tracker. it took everyone the rest of the afternoon to figure out how to file the next bug; the workaround was a shared google doc; the google doc is, three years later, still where some teams report bugs. he is unrepentant.

"i found another unhandled exception."