QOOP GmbH·2023 — present
Flat-Finder
Multi-tenant 3D B2B SaaS
- Role
- Founding Engineer — sole engineer
- Timeline
- Feb 2023 — present
- Stack
- Next.js · TypeScript · Unreal Engine · WebRTC · Cloudflare Workers · D1 + R2 · Leaflet
- Links
- Visit QOOP
Context
The problem
German real-estate developers sell apartments before the building exists. Buyers are asked to commit six-figure sums from floor plans and static renders — and marketing teams burn time fielding the same spatial questions over and over. QOOP needed a product that lets a prospect walk through an unbuilt apartment from a browser tab, while serving many property developers from one codebase, each with their own branding, projects, and access rules.
Ownership
My role
I am the sole engineer on the platform — architecture, backend, frontend, 3D pipeline, infrastructure, and operations. Product decisions are made with the founders; everything technical, from the tenant model to the deploy pipeline, is mine to design, ship, and keep alive.
Solution
Approach
Pixel streaming — built, run, and deliberately sunset
The first version streamed a full Unreal Engine session to the browser — photorealistic walkthroughs rendered server-side and delivered over WebRTC to any device, wired into the platform per apartment unit. I designed and shipped that pipeline and ran it in production for over a year. It worked, but the economics didn't: GPU servers per concurrent visitor, cold-start latency, and mobile fragility. After a structured cost and UX evaluation I recommended sunsetting it in favour of pre-rendered 360° panoramas and in-browser viewers. Killing a system I built myself was the right call — the platform got faster, cheaper, and more reliable.
An SDK so non-engineers ship 3D scenes
Authoring interactive scenes was an engineering bottleneck, so I shipped an Unreal Engine SDK that lets 3D artists — not engineers — author interactive apartment scenes, define camera paths, and publish them into the platform without touching code. That turned scene production from a per-project engineering task into a repeatable content workflow.
A CMS that runs the whole product
I designed a custom CMS that manages every aspect of Flat-Finder: project content, unit data and pricing, photo galleries and video sliders, SVG floor-plan polygons mapped to live unit availability, per-project theming, and lead capture that feeds directly into developers' sales pipelines — all with an edit-history audit log. Tenants self-serve; engineering stays out of the content loop.
Enterprise integrations
Delivered marketplace integrations and co-branded portals with ImmoScout24 (Germany's largest property portal) and Mileway, embedding Flat-Finder experiences inside partner ecosystems with per-partner theming and data exchange. I also built the order-management portal through which agents of one of Germany's largest real-estate marketplaces order 3D tours and 360° media from QOOP — multi-step ordering wizard, admin review workflow, invoicing, and full German/English localization.
Beyond the platform — bespoke client sites
Alongside the platform I ship bespoke marketing sites for individual developments — Pasewalker Straße 96 (Berlin), Joy Living, n48 — each with embedded 360° tours, apartment availability tied to platform data, interactive maps, German/English localization, and investor tooling like AfA tax-depreciation calculators. Animation-heavy builds mixing GSAP ScrollTrigger and Framer Motion where the brand calls for it.
System
Architecture
One Next.js codebase serves every tenant, deployed to Cloudflare Workers with D1 at the edge and R2 for media. Tenancy is resolved per-request in middleware — platform subdomains and customer-owned custom domains both map to white-labeled viewers — and role-based access control spans three tenant tiers: platform admins, developer organisations, and end customers, so one deployment safely serves competing property developers.
- Subdomain + custom-domain white-labeling resolved per-request in middleware, with per-project theming
- RBAC across three tenant tiers, enforced at the data layer
- Edge deployment: Cloudflare Workers + D1 + R2, with a dedicated image-processing service
- 23 API route groups over 12+ data models — projects, buildings, units, galleries, polygons, analytics
- 360° panorama, video (Cloudflare Stream + HLS), and SVG floor-plan viewers in one component system
- Custom CMS with edit-history audit logging, lead capture, and analytics
Results
Outcomes
Dozens
customer projects live in production
1 engineer
entire platform, end to end
3 tiers
of tenants under one RBAC model
1+ year
pixel-streaming pipeline operated in production
- Production platform trusted by ImmoScout24, Mileway, and Formwerk.
- Streaming-to-browser migration cut infrastructure cost and removed GPU capacity as a scaling constraint.
- Scene authoring moved from engineering to the 3D content team via the SDK.
- 140+ components and 23 API route groups built and maintained solo.
Contact
Let's build something great.
Open to Senior, Staff, and Founding Engineer roles — and select freelance engagements. Reply within 24 hours, CET timezone.