For agencies

White-label Three.js and WebGL development for agencies

You sold the 3D experience. Now it needs to ship, on mobile, on time, and the one developer at your agency who really knows WebGL is booked or gone.

  • 01Builds under your brand
  • 02Rescue for stuck projects
  • 03Pre-delivery reviews
  • 04Written scope, every time
Isometric diagram of white-label Three.js work delivered under an agency brand

How I work with agencies

  • [01]

    Your brand on the work. I stay invisible unless you want me on a call.

  • [02]

    Written scope and acceptance criteria before I start.

  • [03]

    Handover documentation the next developer can use.

  • [04]

    NDA and subcontractor agreement on request.

  • [05]

    I say "no" or "wait" when that is the right answer.

Peter Csipkay

Peter Csipkay

Creative frontend developer and creator of Three.js Resources

Runs

threejsresources.com, read by 200,000+ visits a month.

Based in

Near Munich, on CET. Agencies across Europe and North America.

What agencies bring me: white label web development in Three.js

I build the Three.js part of agency projects under your brand, fix the ones that are stuck, and review the ones about to be delivered. I run threejsresources.com, the largest Three.js platform, so I see what breaks across hundreds of projects rather than only mine.

Four kinds of work come up again and again. Scope and quote after a short call.

[01 / Services]
Builds[01]

The 3D hero, the product viewer, the scroll experience, the WebXR piece. Delivered as a documented component the agency's frontend team can maintain after I am gone.

Project rescue[02]

A 3D project that is slow, broken on phones, or stuck before launch. I diagnose it on real devices and send a prioritized fix list. Your team applies it, or I do.

Pre-delivery review[03]

A senior pass on 3D work before it goes to the client: device tests, a code read, and the list of what would otherwise come back as a bug report.

Configurators[04]

The most common request by a distance, so it has its own page.

How subcontracting works

No surprises and nothing verbal. The sequence is the same on every job, whether it is a two-day review or a two-month build.

[02 / Process]
Step[01]

NDA, then a call

An NDA first if you need one, then a short scoping call about the project, the deadline and what has already been tried.

Step[02]

Written scope

A written scope with acceptance criteria, then a fixed price or day estimate sent to you privately. Nothing starts before you have both.

Step[03]

Build and hand over

Work happens in your repo or mine, through your channels if you prefer. Invoicing to the agency, never the end client. You present the work as your own.

Isometric diagram of a stalled 3D build tested across devices with a prioritized fix list

Project rescue

When a 3D build is stuck before launch

Most rescue jobs arrive the same way: it looks right on the developer's laptop, it stutters or crashes on a mid-range phone, and the client presentation is on Thursday. I test on real devices, find what is actually costing the frames, and write it down in the order worth fixing.

You get the diagnosis whether or not I do the work. If your team can apply the fixes faster than I can, that is the better outcome and I will say so.

What the diagnosis covers:

  • Frame timing on real target devices
  • Texture memory and asset weight
  • Draw calls, batching and overdraw
  • What is safe to cut before the deadline
Send me the project

What I will not do

I will not take over from another freelancer mid-flight without a diagnostic first. Half the time the code is fine and the brief was not.

I will not promise a frame rate before measuring the target device. Anyone who does is guessing with your client's money.

I will not build what I think will fail the client. I say so, and propose the version that works instead.

[03 / Limits]

Stack

Three.js, React Three Fiber, TresJS, TSL and WebGPU, GSAP, Next.js and Astro. Vanilla or framework, whichever the agency already runs. More on WebGPU and React Three Fiber if you want to see how I think about them.

What I build
[04 / Stack]

F.A.Q

Frequently Asked Questions.

What agencies ask before the first project.

Working together

How the arrangement runs.

Yes. Your brand, your client relationship. I stay invisible unless you want me on a call, and the work is delivered for you to present as your own.

Only if you ask. The default is that I am a subcontractor to you, I invoice the agency, and the end client never needs to know I exist.

Practicalities

Timing, location and cost.

Reviews and diagnostics usually within a week. Builds depend on scope, and I will tell you on the call whether the deadline is realistic rather than after you have committed to it.

Near Munich, on CET. I work with agencies across Europe and North America, and I am used to a few hours of overlap rather than a full shared day.

Scope and quote after a short call. Every job gets a written scope before a number, because a price without a scope is a guess that one of us pays for later.

Get in touch

Tell me what the project is

Tell me what the project is and what is blocking it. I reply within one working day.

Get In Touch

Let's talk about your project

Tell me what you're trying to build, big or small. I'll reply personally within 24 hours, usually same day.

Drag the corner if you need more room.

A Loom walkthrough, a Figma file, your current site, a repo.

PDF, Word, ODT, text or Markdown, up to 10 MB.

I reply personally within 24 hours — usually same day.

Peter Csipkay

Peter Csipkay

Creative Frontend Developer

Let's connect

Three.js developer and creator of threejsresources.com. I scope, build, and ship the work myself — no middlemen, no handoffs.

Based in

Munich, Germany