You. The system and its spec live in your repository from day one. Close the project and you keep both — and it keeps running without us.

Who gets access to our systems?

We prepare the changes — to spec — but only your team applies them. Outside specialists never get access to your live systems.

How do you handle our data?

Read-only access to what the work needs, nothing more. An NDA before you share anything sensitive. Our verification gates reject on missing config by default — they never silently pass.

What happens after delivery?

The system stays yours and runs without us. If you want ongoing support, there's a subscription: the spec stays current, architecture answers the same day, a monthly review.

ENGAGEMENT

Start a project

Tell us what you're building. Every brief gets a considered reply within two working days.

Two ways in

Discovery3–4 weeks · OpenSpec deliverable

We turn your idea into a structural artifact — an OpenSpec capability map, a domain model, and a first-pass render. You leave with a blueprint you own, whatever you decide next.

Full engagementSprint-based · discussed after brief

A curated team builds with you, two weeks at a time.

Not sure which? Say so in the form — we'll help you choose.

What happens after you send this

We read every brief ourselves — no intake bot. Within two working days you'll hear back from Pavel: a short, honest read on whether the studio is the right fit, and what the first step would cost.

Pavel Rapoport · Rapoport Studio

You'll contract with Rapoport Studio SRL — a Moldovan company and a Moldova IT Park resident, registered in Chișinău.

The brief

What you're building, who it's for, and why now.

Brief

What hurts today, who feels it, why now.

0 / 2,000

How did you hear about us?

We use your details to respond to your enquiry — see our privacy notice ↓.

Privacy notice

Who's collecting: Rapoport Studio SRL · legal@rapoport.studio
What we collect: Name, email, company (optional), role (optional), engagement interest, project type, budget range, timeline, project brief, and referral source.
Why: To respond to your enquiry and, if there's a fit, propose an engagement. We stop the conversation if there's no fit.
Legal basis: Legitimate interest (GDPR Art. 6(1)(f)): responding to inbound business enquiries from prospective clients and partners.
Where it goes: Stored in Supabase (EU region) and reviewed by Pavel Rapoport. Not shared with third parties for marketing.
How long we keep it: Up to 24 months from last contact, then anonymised.
Your rights: Under GDPR Arts. 15–22: access, rectification, erasure, restriction, portability, objection. Write to legal@rapoport.studio.

Before you reach out

Who owns the result?: You. The system and its spec live in your repository from day one. Close the project and you keep both — and it keeps running without us.
Who gets access to our systems?: We prepare the changes — to spec — but only your team applies them. Outside specialists never get access to your live systems.
How do you handle our data?: Read-only access to what the work needs, nothing more. An NDA before you share anything sensitive. Our verification gates reject on missing config by default — they never silently pass.
What happens after delivery?: The system stays yours and runs without us. If you want ongoing support, there's a subscription: the spec stays current, architecture answers the same day, a monthly review.