Pagenth & runevr, built with the door open.
Real-time sync, render parity, the load-bearing stuff.
What running a studio taught us about shipping.
A small, senior product team — from Yerevan, for clients anywhere.
Product studio
We take software to production.
The team behind Pagenth and runevr — two products we build, own, and run — takes your idea, or your half-built app, and ships it. For real users, in production.
● Available for new projects
// where are you right now?
Start where you are.
I have an idea.
You know what you want to build. We take it from a blank page to a launched product.
Start here →It's half-built or broken.
An AI tool or a past team got you 70% there, then it stalled. We finish it and make it production-grade.
Get it unstuck →My company needs a system.
Your operation runs on spreadsheets and disconnected apps. We build the internal platform it should run on.
Explore systems →I need an ongoing team.
A senior product team — design, engineering, QA — on tap, without hiring one.
Work with us →// work
Two products. Ours.
Most studios show you client logos. We show you products we built from nothing, own, and operate every day.
runevr
A real-time workspace where creative teams chat, record, and review media together.
// services
What we do.
Idea → production
Bring the vision. We design, build, and launch a real product — not a throwaway prototype.
Rescue & finish
A half-built or broken app, taken to production. We start with a fixed-fee audit, then finish it right.
Custom operational systems
The internal platform your company runs on — pipelines, data, chat, team workspace — built on our proven engine.
Fractional product team
Design, engineering, and QA as an ongoing partner. Senior output, no full-time hire.
Cloud & cost optimization
We ship, scale, and secure your production infrastructure — on AWS, Vercel, and Cloudflare — and cut the cloud bill. Fixed-fee AWS cost audits to start.
An agency asks what to build. A studio tells you when the answer is don't build that.
We build and operate our own products, so we live with every decision — the feature that shipped, the one we killed, the maintenance three months later. You get judgment, not just hours.
// craft
We sweat the interface.
Our design lead — a decade in animation — hand-crafts every screen, then lives in it as your users will, long before it reaches you. The friction gets found and fixed on our side, so what you ship already feels right.
// how we work
How we work.
Diagnose
A short, fixed-fee discovery sprint or code audit — so we both know exactly what we're building before anyone commits.
Design
We shape the product and the plan. You see the direction early, not after months.
Build & ship
Senior team, async by default, shipping to production in focused sprints. First working preview in days.
Run or hand over
We stay on as your team, or hand you a clean, documented codebase you fully own.
We work async and write things down — clear specs, clean code, short Looms, not endless calls. Guaranteed daily overlap window when you need us live.
// studio
Where Rubber Boots comes from.
We started in animation — a studio that made over 2,000 short films and, along the way, the pipeline tools and management systems that kept it running. One of those internal tools grew into runevr. Building for our own creative teams taught us exactly where software breaks under real people doing real work.
The name is a private joke that stuck: when a project turned to mud, we'd say we'd put our rubber boots on and walk through it. That's still the job — the parts that are hard to get right are the parts we're here for.
Today we're a small, senior team — engineering, design, QA, growth — building from Yerevan for clients anywhere.
// questions worth asking
Questions worth asking.
How much does a project cost?
Fixed-scope builds are scoped precisely before you commit; rescues begin with a low-cost audit. You get a real number after a short diagnostic — never a guess.
How long?
First working preview in days. Most MVPs and rescues run 4–10 weeks. We give you a real timeline after the diagnostic.
We already have a team or a codebase.
Good — we work alongside in-house teams and inherit existing codebases all the time.
Do we own the code?
Completely, from day one — code, repos, cloud accounts, domains.
You're a small team. Is that a risk?
It's why every person on your project is senior and accountable. You talk to the people building it, not an account manager.
Where are you based?
Yerevan (UTC+4). Strong overlap with Europe and the Middle East, a guaranteed daily window for everyone else, and async discipline so progress never waits on a meeting.
// field notes
Read Field Notes →Field Notes.
Building in public, the hard problems most studios hide, and the road from animation to software.
Dev logs, in the open
How Pagenth and runevr actually get built — decisions, dead ends, and the fixes.
First notes soonThe 30% AI can't do
Real-time sync, render parity, the load-bearing engineering under a demo.
First notes soon2,000 films to shipping code
What running a studio taught us about building software people rely on.
First notes soonHave something to build — or something that's stuck?
Tell us where you are. We'll tell you honestly if we can help, and how.