About — Nomad

Why it exists

The tools got good. The workflow did not.

Image models became extraordinary in about eighteen months. What did not arrive alongside them was a way to use one inside an architectural process — where a render is not a picture you generate, but a decision you are making about a building that already has a geometry, a client, a stage and a deadline.

So the work goes into a chat window. You describe the building you have already modelled. You get something adjacent to it back. You describe it again. The roofline moves. Nobody can say what was asked for last Tuesday, the prompt lives in someone's message history, and the render that was almost right cannot be found.

Nomad is the other shape: a canvas where the reference, the words, the render and the sheet are all objects you can see at once, wired together, and where the thing you asked for is written down next to the thing you got.

What we believe

Five rules, and the evidence for each.

These are not values we wrote for this page. They are decisions already made in the product, and each one cost something to hold.

The building does not change

Every prompt Nomad writes states the geometry positively and puts all motion in the light, the weather and the camera. A render that quietly moves a roofline is worse than no render, because it looks like an answer.

Why the camera moves are bounded, and why a clip says what it will not do.

Nothing spends without saying so

Every action that costs credits shows the number on the button first. The pre-flight check that stops a bad render is free, and a failed call refunds itself.

When a provider charges for something we did not deliver, we say so and tell you where to find it.

Why a clip that fails names the job id, and why the run is traced step by step.

Refuse honestly

A PDF with no text layer says so rather than inventing contents. An empty sheet says there is no picture on it. A model that cannot make what you asked for is told to you before the credits move, not after.

Why MiniMax stops at two pictures instead of quietly using two of your five.

Plain words, not abbreviations

"Keep its shape", not AUTO. "The film opens on this", not FL2VA. You spent ten years learning architecture; you should not have to learn our vocabulary to get a picture out of it.

Why the inspector reads like a sentence and controls appear only when they apply.

The model is not the product

Seven models sit on the canvas and you choose per node, never per project. We write the prompt in the grammar each one was trained on, so switching engines is a decision about the picture rather than a research project.

When a better model arrives, it should be a line in a release note, not a migration.

Why every engine has its own prompting guide built in.

Your work is yours

A project is a file you hold. Your renders, your prompts, your brief and your references travel with it. Nothing is trained on your drawings.

Why a project saves as one file you can put anywhere.

What is different

Made by people who have to use it on Monday.

It is a canvas, not a conversation

The reference, the prompt, the render and the sheet are objects with wires between them. You can see what fed what, change one word, and re-run a single node without losing the others. A chat window cannot show you the shape of a set — a canvas is the set.

It writes the prompt, in the grammar of the model you picked

The same sentence becomes named fields and cut timestamps for MiniMax, flowing prose for LTX, and explicit time phases for FLUX past eight seconds. You never see any of that. You pick an engine and the writing follows, because a prompt written for one model reads as noise to another.

Stills and video are the same workspace

A render becomes the opening frame of a camera move without leaving the canvas. Several renders become the shots of a film. One render becomes a storyboard, and the storyboard becomes a reel, one clip per frame — with nothing spent on video until you have seen the frames.

The prices are the provider's, plus a stated margin

A credit is a cent. Every model's rate is published on the pricing page against what it actually costs us to serve. We would rather you knew that a twenty-second clip is expensive because it is expensive, and drafted it cheaply first.

Small on purpose, for now

There is no support tier, no sales team and no roadmap deck. There is a practice in Dubai that uses this on real projects, and an email address that reaches the two people who built it. That will not scale forever. It is true today.

Who it is for

Practices that draw more than they render.

Studios of one to fifty who make visual decisions constantly and do not have a visualisation department to make them with.

Architects competing against practices with three times the staff

No dedicated visualiser — the person who models it also renders it

Stretched across competitions, concept design and client meetings in one week

Tired of exporting, uploading, describing and re-describing the same building

Want the speed without the drift — the render must be the building

Interior and landscape teams working the same way, on the same project

Behind the name

Nomad

An architect's work moves. It starts in a model, becomes a screenshot, becomes a reference, becomes a board, becomes a conversation in a meeting room, and comes back as a note to change the light. Nothing stays where it was made.

Most tools assume the opposite — that work lives in one application and visits the others. Nomad is built for the moving: the canvas takes what you already have, in whatever state it arrives, and gives it back in whatever form the next room needs.

The name is also a description of how it is made. It comes out of a small practice in Dubai working across the Gulf, Europe and North America, on projects that rarely sit in one place either.

And it is a promise about lock-in. A project is one file. Take it with you.

Where we are

Honestly, early.

Every other page on this site describes what the product does. This one says what it is, which matters if you are deciding whether to put a live project through it.

Stage

Soft launch. A small number of practices are using it on real work while we watch what a month actually costs to serve.

Team

Two architects, and no one else. The people who answer your email are the ones who wrote the code and drew the buildings it was tested on.

Funding

None taken. Nomad is paid for by the practice that built it, which is why the pricing has to work rather than merely look attractive.

Registered

Under a UAE trade licence, in Dubai.

What is finished

The canvas, the prompt engine, storyboards, sheets and presenting, seven models across stills and video, camera moves, films and reels.

What is not

Region-marked editing, the motion timeline and external content binding are display-only. They are listed as such in the documentation rather than hidden.

Co-founders

Two architects, and no one in between.

Nomad is built by the two of us, in Dubai, around the projects we are already drawing. Write to it and one of us reads it — there is no support queue to route you through.

Arief

Architect

Writes the code. The canvas, the prompt engine and the pricing all came out of needing them on live work and not finding them.

Fahima Zabeen