Independent software studio · products & client work

We build software, run it in production
and take on your project too.

SSV Studio is an independent practice led by Serhii Skrynnikov. Five of our own products serve real users right now, in many languages and with no single market they are built for — you can open every one of them below. The same hands that built and operate them are available for client work: web applications, Telegram Mini Apps, Android software and the infrastructure that keeps them up.

Products in production
5
In development
2
Platforms
Web · Telegram · Android
Delivered end to end
Design → code → ops

01 Products in production

Our own software, serving real users. Every link opens the live product — nothing here is a mockup. Read how each one is built →

Complevia

complevia.fyi
Live

A habit tracker built on time windows instead of alarm times. A habit gets a window and you answer it whenever you are free; an unanswered prompt escalates, but only up to a ceiling you set. A habit you cannot keep this month is paused, not deleted.

  • The wedge: an alarm snoozed at 7:02 is one you never see again — a window has no single minute to miss.
  • Two ways in: run it inside Telegram with nothing to install, or install the Android app. No account to create either way.
  • Reach: 21 languages, free, currently v1.3.0 — 4.8 MB, Android 8.0+.
  • Kotlin
  • Jetpack Compose
  • Android
  • Telegram Mini App

SignalOps

signalops.one
Open beta

Turns a team's Slack, Teams or Discord — plus Jira or Linear — into decisions, action items, risks and open questions, each traced back to the message it came from. The product a manager reads instead of scrolling.

  • Approach: deterministic tracking arithmetic first, then one AI pass over the linked signals.
  • App: app.signalops.one — OAuth, workspaces, scheduled digests.
  • State: free open beta, no card.
  • Next.js
  • Prisma
  • Postgres
  • Claude API
  • Paddle

MSGView

msgview.app
Live

Opens and converts Outlook .msg and .eml files that the new Outlook refuses to open without a Microsoft 365 subscription — including recovering attachments out of winmail.dat (TNEF). Exports to PDF, HTML, EML and text.

  • The wedge: the file never leaves the device — the parser runs in the browser tab.
  • Engine: @msgview/core, pure isomorphic JS with zero runtime dependencies.
  • Reach: 13 languages, search-led acquisition, free and unlimited.
  • JavaScript
  • MS-CFB / MAPI
  • TNEF
  • Tauri desktop
  • Docker

PubOpener

pubopener.pro
Live

Viewer and converter for Microsoft Publisher .pub files, riding the retirement of Publisher (end of support October 2026). Converts to PDF, PNG, HTML or text without an install and without an account.

  • Hard invariant: the backend has no endpoint capable of receiving a file.
  • Shape: static site plus a WebAssembly engine in-tab; a thin Rust control plane for licensing.
  • Model: free tier plus a one-time unlimited unlock — no subscription.
  • Astro
  • TypeScript
  • WebAssembly
  • Rust · Axum
  • Postgres

ZALUPA Clicker

zalupa.quest
Live

A Telegram Mini App tap-game with a public leaderboard and a capped emission. The in-game coin is a score counter — no payouts, no blockchain, and the withdraw button is deliberately disabled and says so.

  • Rule: the economy is server-authoritative; the client only draws what it is told.
  • Game host: app.zalupa.quest, opened from the bot.
  • Reach: 10 languages, with a translation gate in the build.
  • Fastify
  • React · Vite
  • Prisma
  • Telegram WebApp
  • Stars

02 In development

Being built right now. Nothing public to try yet.

Underground

Android · events, tickets and the people going
In development

What is on tonight, the ticket for it, and the people going — in one app instead of three services. Listings, a box office and a social layer around concerts, parties and club nights, built for any city's scene rather than one country's.

  • The point: a ticket should not be a bet on the promoter. The design holds the buyer's money in escrow until the event actually happens, and returns it if it does not.
  • Shape: a Kotlin and Compose client, a Rust API, and a separate admin for organisers. Google sign-in only, dark theme only.
  • Where it is: client, API and organiser admin all exist internally. Nothing is public, and no date is announced.
  • Kotlin
  • Jetpack Compose
  • Rust · Axum
  • PostgreSQL
  • Next.js admin

Dark Forest

Game · in development
In development

A game, currently being built. We are not describing it yet — the first playable demos are coming soon, and they will say more than any description would.

03 Work with us

The same practice that ships the products above is available for your project — as the whole team, or as the missing part of yours.

Product engineering, end to end

An idea becomes a deployed product: architecture, implementation, infrastructure, release and the operating afterwards. One person accountable for all of it, so nothing falls between roles.

Privacy-first web tools

File viewers, converters and editors that run entirely in the user's browser — WebAssembly where it needs speed. No upload endpoint means nothing to breach and nothing to store.

Telegram Mini Apps & bots

Server-authoritative mini apps with real economies, leaderboards, Telegram Stars payments and many languages. Two of ours are live; we know where this platform bites.

Android applications

Kotlin and Jetpack Compose, signed release builds, store delivery and the release plumbing that usually gets discovered a week before launch.

Self-hosted infrastructure

Containerised deployments, automatic TLS, health checks, structured logs, backups and a rollback that has actually been performed. Your servers, your data, no vendor lock-in.

SEO-led product growth

Technical SEO, localised landing pages and search-driven acquisition — the channel that brings our own products their users, applied to yours.

How an engagement runs

  1. A call and a written scope. Before any code, what is being built and what "done" means are written down, in your words, and agreed.
  2. Small slices, each one deployable. Work lands in pieces you can open and use, not in a three-month silence ending in a demo.
  3. You see progress, not status reports. Every slice ends with a URL or a build, plus what changed and what is next.
  4. The code and the servers are yours. Repository, infrastructure, domains and documentation are handed over as we go — never held hostage.
  5. A runbook, not a goodbye. Whatever ships comes with instructions for running, deploying and rolling it back without us.

Building it stopped being the hard part.

Code is faster to produce than it has ever been. The week after launch is exactly as hard as it always was: the certificate expires, an update breaks something and there is no way back, the disk fills at 3am and no alert goes off because nobody set one up. That part did not get cheaper — and that is the part we sell.

SSV Studio is one engineer, Serhii, who built and still operates the five products above. You always get the person who knows your system rather than a first-line ticket, which is also why the plans below name a real response window instead of claiming 24/7. You get the price before the work starts, and it does not move because something took longer than we thought.

Your app can stay exactly where it is or move onto our server — we will tell you which is cheaper for you. The code, the domain and the accounts stay in your name. Cancel and you get the keys and a written runbook, and the billing stops.

Fixed price, agreed before we start

Production check

$450 report in 5 working days

You built something with an AI tool — or someone did — and it is live and people are using it. It might be on Vercel, Railway, Render, Fly, Supabase, a server someone set up for you, or something you could not name if asked. Send the link. We read the code and wherever it is running, and write down what breaks first, what each fix costs, and the order to do them in.

One codebase, one environment. Five to ten pages in plain language, yours either way. The $450 comes off anything you book within 90 days.

Make it operable

$1,500 – $3,500 one number after the check

For something that got built fast and now has to stay up while people depend on it. When we are done: it restarts by itself if it crashes; if an update breaks it we put the last working version back within minutes, and we do that once in front of you before calling the job finished; your data is backed up nightly and we have restored a backup to prove the backup works; the padlock in the browser renews on its own instead of expiring on a Sunday; and when something goes wrong there is a written record of what happened, so nobody is guessing.

In our words: containerised deploy, automatic TLS, health checks, structured logs, a tested restore, one-command deploy and rollback — plus a runbook written for someone who is not us.

Build it

$3k – $8k per stage

From an idea, or from a project that stalled. Priced one stage ahead and paid per stage, and you own everything built so far if you stop after any of them.

Most first working versions land in that range. Bigger products carry on in stages of the same size — never one number for the whole thing.

Monthly, cancellable any month

Watch if it only has to keep running. Operate if it keeps changing. Partner if we are effectively your engineering team.

Watch

$250/month

  • Starts after a Production check — we do not monitor a system we have not read
  • Checked every minute, day and night; if it stops answering you hear it from us, not from a customer
  • Hosting and certificates, renewed before they expire
  • Backups, and a restore actually performed every quarter
  • Dependency and security updates
  • An answer the same working day
  • When something breaks, a fixed price to fix it before we touch anything — usually $250 to $750, quoted the same day

Operate

$600/month

  • Everything in Watch
  • Something is down: we start within four hours, 09:00–19:00 Kyiv time, Monday to Friday — outside that, first thing the next morning
  • Small changes and fixes to the system we operate, up to four a month and each a day or less, never quoted one by one
  • Anything bigger gets a fixed price before we start
  • A monthly note: what changed, and what we are watching

Partner

$1,200/month

  • Everything in Operate
  • Two days of development every month, reserved for you and booked at the monthly call — unused days do not carry over
  • Your incidents are picked up before any Operate or Watch work, and Partner is capped at two clients so that means something
  • A call every month about what to build next, and what to drop

One project at a time, support alongside it. Everything runs from your repository, with a runbook any competent engineer can follow — so "what if you disappear" is already answered in writing rather than promised. Tell us your timeline in the form below and you get a start date, including "not soon" if that is true.

There is no agency between you and the person doing the work: no account manager, no bench, no sales floor to feed. One person does the design, the code, the servers and the pager, so nothing is paid for twice and nothing is lost between roles.

We do not sell an uptime guarantee with penalties attached. One person cannot honour one, and anybody this size offering you one is selling you a refund rather than a fix. What you get instead is a start time, in writing, above.

There are no client logos on this page. What there is instead: five products that have been running for months, that we deploy and patch ourselves, and that break on our own time rather than on somebody else's.

04 How we build

Six rules that decide most of the arguments before they start.

01

Local-first by default

If a user's file can be processed in their own browser tab, it is. There is no upload endpoint to breach, and the privacy claim is structural rather than a promise in a policy page.

02

The server decides

Anywhere money, score or state is at stake, the client draws and the server rules. A client that can decide an outcome is a client that can be edited.

03

Ship the engine, then the paint

The thinnest slice that proves the product end to end goes first — one ugly path that actually works beats a finished layer with nothing behind it.

04

Built to be operated

Containerised, one artifact for every environment, config read at runtime, health checks, structured logs, and a rollback that has actually been performed — not a plan to write one.

05

Whoever writes it does not certify it

Author and reviewer are never the same identity, every gate is read from CI rather than claimed, and nothing above a trivial defect ships.

06

Own the whole stack

Design, code, infrastructure, domains, search visibility and the on-call pager sit with the same person. Every product on this page runs on one server we rent and administer ourselves behind a shared reverse proxy with automatic TLS — which is why a new product costs a config block, not a contract.

Start a project

Tell us what you need built. You get a written scope and a straight answer on whether it is worth doing — within one working day.

What do you need?
Budget optional
Timeline optional

Straight to a person, not a queue — answered within one working day.