3D & engineering tooling in the browser
Large models parsed, rendered and interrogated client-side, with real geometric analysis rather than a picture of geometry.
Proof: the BIM reviewer aboveSoftware studio · London, United Kingdom
We build the software other people depend on.
Production systems that carry real work — real-time video platforms, offline-first business software, commerce that crosses borders, the back office behind all of it, and 3D tooling that runs in a browser tab.
Web Mobile Desktop E‑commerce Real‑time video Back‑office systems 3D & BIM
0 third-party requests 0 trackers 0 cookies this page, verifiable in DevTools
One of them, running 3D & BIM tooling
01 / Proof, not adjectives
Most studios describe their work. Here is one of ours, doing it.
We picked this example because it is the one we are free to show you in full. It solves a construction client's model-review problem and runs entirely in the browser — no server, no upload, no account. The same standard sits behind the video, commerce and back-office work further down.
-
01
It opens a real model.
An IFC2X3 file exported from Revit — 779 elements, 416,542 triangles, five levels — parsed and on screen in under a second. Not a converted preview: the actual file, read in the browser.
-
02
It finds every hard clash.
586 of them, in 449 milliseconds. And it measures them honestly: both solids are voxelised so the numbers describe where geometry genuinely interpenetrates, not where two bounding boxes happen to overlap. That distinction is the difference between a usable report and a thousand false positives.
-
03
It audits the model before site does.
Structural and data health checked against the file itself, so problems surface in the office rather than as an RFI from a contractor standing in the building.
-
04
It answers "what is this?"
Click any element and read its IFC identity, classification and full property sets — the payload behind a model comment or an RFI — pulled directly from the source file.
-
05
It cuts through anything.
Live section planes on any axis, elements isolated or ghosted, levels exploded to see how a building actually assembles.
-
06
It speaks the client's language.
The German build is written in DACH BIM vocabulary, not translated word for word: property sets are Merkmalsgruppen, MEP is TGA, an issue is a BCF‑Ticket, a federated model is a Koordinationsmodell. An Austrian coordinator reads that as native. A literal translation reads as foreign and undoes the credibility the tool exists to build.
No server. No upload. No CDN. No account. The whole thing runs offline in a meeting room with bad wifi — because that is where it had to work.
That is the standard we build to, and it is why this page loads the way it does. If you want a walkthrough with your own model, ask us for one.
02 / Client work
Delivered for people who paid for it, and still running.
The tool above is ours. This part is not — and it is the part that matters more, because it is the part someone hired us to do.
We have shipped a trilingual e-commerce platform — English, German and Arabic with full right-to-left layout throughout — carrying retail and wholesale pricing tiers, integrated card payments, EU VAT handling and audit-ready invoicing. It is operated day to day by the client's own team. We are not in the loop for a price change, a new product line or a VAT rate.
Alongside it: live video platforms, mobile and desktop applications, the secure systems of record behind daily operations, and the internal consoles that keep them running.
We do not publish client names or logos. Those systems run other people's businesses, and that is their story to tell, not our marketing. It is also how we would treat yours. Ask us for specifics and we will walk you through the relevant work directly — including what went wrong and what it cost to fix.
- MyVault Pro
- Offline password vault
- One More Tile
- iOS & Android
- The Kiss App
- iOS & Android
- RevuMeet
- Video platform
Consumer apps carry no client confidentiality — they are ours, and they are in the stores under our own name.
03 / What we build
Six things we have already shipped.
Everything here is running today — in our own products or in client systems. Nothing on this list is aspirational.
Real-time video & collaboration
Multi-party video, screen sharing, recording and transcription built into your product — not an embedded third-party widget.
Proof: RevuMeet, our own platformOffline-first desktop software
Systems that run on the customer's own machine, with their data on their premises — no cloud dependency, no monthly hosting, no vendor to outlive.
Proof: Mizan, in developmentCommerce that crosses borders
Stores selling in English, German and Arabic with full right-to-left layout, retail and wholesale tiers, card payments, EU VAT and audit-ready invoicing — run day to day by the client's own team.
Proof: live client platformSecurity designed in, not bolted on
Row-level security in the database, so authorisation is enforced where the data lives rather than in each client. Every table denies by default and is reachable only through audited functions — the wrong person cannot read the wrong row from any screen, any app, or a leaked API key.
Proof: our security policyThe back office that runs it all
Consoles, approval flows, invoicing with real payment rails and the unglamorous internal tooling a business actually operates on, designed for the people using it every day.
Proof: our own console & invoicing04 / Our own systems
We build our own products, and live with the consequences.
Two systems we own end to end. We run client work on them, which means we find the sharp edges before your users do.
Flagship · in development
Mizan — ميزان
A complete business-management platform for small companies — double-entry accounting, inventory, sales and purchasing, HR and payroll — that runs entirely on the customer's own computer.
No cloud account. No monthly hosting bill. No dependency on us continuing to exist. For a small business that has watched three SaaS vendors raise prices or shut down, that is not a feature — it is the whole argument.
- Platform
- .NET 10 · Avalonia
- Data
- On-premise, customer-owned
- Languages
- 4, incl. Arabic RTL throughout
- Network required
- None
In production
RevuMeet
Our own multi-party video platform. We did not wrap someone else's SDK — we built the media path, and that is why we can tune it. Screen sharing has an optimise for text or motion choice, quality tiers switch make-before-break so the picture never drops, and the spotlight follows whoever is actually speaking.
Recordings come back as transcripts attributed to the person who said it. Invitations arrive as native calendar requests with a working Accept button, and the replies are read back automatically so you can see who is coming.
- Media
- WebRTC · simulcast · SFU
- Transcripts
- Speaker-attributed
- Invitations
- Native calendar + RSVP tracking
- Runs
- Our own client meetings
05 / How we work
A process you can hold us to — in the contract, not on a slide.
01
Discovery
Scope, users, constraints and what "done" means — agreed in writing before any build begins.
02
Build in the open
Working software you can see as it takes shape, not a reveal at the end.
03
30-day warranty
Every engagement ends with a defect warranty. If we broke it, we fix it, at no cost.
04
It becomes yours
On payment the intellectual property assigns to you. Your code, your product, your future — with or without us.
These are terms in our contract, not promises on a website. Read the Terms of Service before you talk to us, and hold us to them afterwards.
06 / Company
A small studio, on purpose.
Small means the people you talk to are the people who build your product. There is no account layer between you and the engineering.
We publish our own software because it keeps us honest: we live with our engineering decisions long after launch, and we bring that standard to client work. We are deliberately conservative about technology — proven platforms, mainstream databases, established payment and infrastructure providers. Fewer moving parts means fewer surprises, and a system your people can maintain, hire for and rely on years after handover.
Two things you would find out anyway, so we will say them first. RevuFlex Ltd is a young company — the registration number gives that away — and the registered office in Covent Garden is a formation agent's address, as it is for a large share of UK companies. Neither is a secret and neither is what you should be relying on.
Rely on the contract instead: the intellectual property assigns to you on payment, the warranty is a clause with a number attached, and the work is inspectable before you commit a penny. A letterhead is not evidence. Terms you can enforce are.
- Company
- RevuFlex Ltd
- Registration
- No. 17120351, England & Wales
- Registered office
- 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ
- General
- hello@revuflex.com
- Legal
- legal@revuflex.com
- Security
- Disclosure policy
What we are not claiming
The limits, before you ask.
We are not a large team.
If you need forty engineers in six weeks, we are the wrong studio and we will say so in the first email rather than the third month.
We have no household-name logos to show you.
The work is real and running, but it belongs to private businesses. If logo validation is what your board needs, we cannot give you that.
Mizan is not finished.
It is in development, and we call it that. We are not going to screenshot half-built modules and present them as a shipped product.
07 / Contact
Tell us what you want to build.
Describe the problem in a paragraph. You will get honest questions back, not a sales deck — and if we are the wrong studio for it, we will tell you that too.
Security researchers: security@revuflex.com · /.well-known/security.txt