For Indian practice
The floor plan is compiled, not guessed.
Describe the building in plain language. Naksha writes it as a precise plan, compiles that plan to a real drawing, and checks it against the National Building Code and the bye-laws — with the clause cited for every result. The model never draws the wall; it states the room, and the geometry is derived. To the millimetre.
Free Beta for macOS, Windows & Linux · licence issued on request.
The gap
The concept is fast. The sanction drawing is not.
You can sketch a workable layout in an afternoon. Turning it into a drawing that is dimensionally exact, internally consistent, and defensible against the bye-laws is the part that eats the week — chasing setbacks, re-checking FAR and coverage, making sure the DXF a client's office opens matches the print you approved.
The "AI floor plan" tools that promise to skip that work produce an image — no dimension you can trust, no wall you can measure, nothing a plans examiner would accept. It looks like a shortcut and turns into a redraw. Naksha is built the other way round: the plan is a document to be compiled, not a picture to be generated. That one decision is what makes the exact dimensions, the compliance check, and the clean DXF actually hold.
How it works
One brief. Five deterministic steps. A drawing you can measure.
You write the brief
Describe the building the way you'd brief a junior: the plot, the road side, the setbacks, the rooms and their sizes. Plain language.
The model writes the plan as code
Running locally under your own Claude login, it authors a declarative document — not a drawing. A room states its interior size; the walls grow outward from it.
The engine compiles it
A deterministic compiler turns that document into geometry and into a drawing — in integer millimetres. A mistake doesn't crash it: the compile succeeds and reports the exact field and line to fix, with a hint on how.
Three reviewers check it
Independent agents audit the result — one over geometry, one over dimensions, one over code compliance. One re-derives the compliance numbers and checks the checker.
You preview and export
Preview the SVG in the app; export the DXF for AutoCAD. Both come from the same in-memory drawing, so they cannot disagree.
Precision & determinism
Exact by construction, not by luck.
The model never draws geometry
It writes a document that states intent — room sizes, positions, openings. Every wall, corner, and dimension is derived by the compiler. No length is ever invented by a language model, so none can be wrong by 3 mm and stay hidden.
A float is refused, not rounded
A room written in metres — [3.6, 4.2] — is rejected outright, not quietly stored as 3 mm. A plan is a document someone will build from; the engine refuses the ambiguity rather than guessing at it.
Preview is evidence about the export
The SVG you review and the DXF you export are rendered from a single in-memory drawing. There is no second renderer and no post-processing of one on its own — so the preview cannot drift from the file.
Compliance
Checked against the code — with the clause cited.
Setbacks, FAR, ground coverage, and room minima are computed directly from your plan against a versioned ruleset built on the National Building Code and the Model Building Bye-Laws, and configurable to local development-control rules across India. You don't get a verdict — you get a result with its source, so you can check the reasoning against the actual bye-law.
It opens in AutoCAD — and matches what you approved
Export a DXF and open it like any other drawing. Because the DXF and the on-screen SVG come from the same document, the geometry you signed off in the preview is the geometry that opens on a colleague's machine — to the millimetre, in the units the drawing was authored in. No re-tracing, no reconciling two files.
Runs on your machine, under your own login
Naksha is a desktop app. The compiler and the agents run locally, and it uses your own Claude Code login — you sign in the way you already do. The app never renders a login screen, never asks for an API key, and never handles your credentials. Your plans are files on your disk, not uploads to ours.
Questions
What a careful professional asks first.
How accurate are the dimensions?
Exact, by construction. The drawing is compiled from a document in integer millimetres; the model never draws geometry, it states room sizes and the engine derives the rest. There is no floating-point rounding and no length invented by a language model. A plan that tries to use metres — a float — is rejected rather than silently converted.
Does this mean my drawing is approved or legally compliant?
No — and any tool that claims that is misleading you. Naksha checks your plan against a versioned ruleset built on the NBC and Model Building Bye-Laws and shows the results with the clause cited for each one. That is a rigorous, auditable check. Approval is granted by a sanctioning authority, not by software. Naksha makes the compliance work faster and traceable; it does not replace the authority or your professional judgement.
Will the DXF open cleanly in AutoCAD, or will I redraw it?
It opens as a normal DXF and matches your preview exactly — because the SVG and the DXF are rendered from the same in-memory drawing. There is no second renderer that could drift. The geometry you approved on screen is the geometry in the file.
Does it replace me as the architect?
No. Naksha drafts and checks; it does not stamp, submit, or take professional responsibility. It removes the repetitive dimensional and bye-law work so you spend your time on judgement — the plan is editable text you stay in control of at every step.
Which codes and regions does it cover?
The compliance engine is built on the National Building Code and the Model Building Bye-Laws, and is designed to be configured to local development-control rules across India's states and regions. The exact rulesets shipped are versioned and cited in-app, so you always see which clause a result comes from.
Is my data private?
Naksha is a desktop app that runs on your machine, under your own Claude Code login. It never handles your credentials and never shows a login screen. Your plans are files on your disk.
What do I need to run it, and what does it cost?
A desktop machine (macOS, Windows, or Linux) and a Claude Code login. Naksha uses your own Claude login, so your Claude usage is billed by Anthropic under your existing plan — Naksha does not resell it. Pricing for Naksha itself is arranged directly with us; join the launch list and we'll be in touch.
Download · Beta
Try the Beta today.
Naksha is in Beta. The app is free to download and licence-gated — email us and we'll issue you a Beta licence key so you can run it. Prefer to wait for the stable 1.0 release? Leave your email and we'll tell you the day it ships.
v0.9.0 · Beta · macOS & Windows builds are not yet code-signed — on macOS, right-click the app → Open on first launch.
Launch list
Be first when Naksha ships.
We're preparing the first customer-ready release. Leave your email and we'll tell you the day it's ready — and nothing else.