Studio

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. Four of our own products serve real users right now — 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.

Start a project See what's live
Products in production
4
Live domains
6
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.

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
Open MSGView

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
Open PubOpener

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
Open SignalOps

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
Open ZALUPA

02 Coming soon

Built and running internally, not yet open to the public.

Complevia

Android · recurring action tracker
Coming soon

A tracker for the things you have to do again and again and keep forgetting — service intervals, renewals, medication, maintenance. Built, signed and installable; the public release is waiting on store delivery.

  • Kotlin
  • Jetpack Compose
  • Android

Cyber Fighting

Telegram Mini App · real-time PvP
Coming soon

Real-time first-person duelling inside Telegram. A deterministic 20 Hz engine shared by server and browser, so a bout survives a deploy and resumes mid-fight — and the server, never the client, decides every hit.

  • TypeScript
  • Deterministic tick
  • WebSocket
  • Postgres

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.

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 per 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 our own hardware 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 — usually within two working days.

What do you need?
Budget optional
Timeline optional

Straight to a person, not a queue — usually answered the same day.