𝐏𝐀𝐋𝐈𝐂𝐀𝐃: 𝐋𝐈𝐆𝐇𝐓𝐖𝐄𝐈𝐆𝐇𝐓 𝐂𝐀𝐃 𝐖𝐈𝐓𝐇 𝐀𝐍 𝐎𝐏𝐄𝐍 𝐊𝐄𝐑𝐍𝐄𝐋 𝐔𝐍𝐃𝐄𝐑𝐍𝐄𝐀𝐓𝐇.

I ran PaliCAD through my TPS REPORT research automation pipeline, because the question on a real job is never just "does it model?"

It is: can I move the geometry, can I trust it offline, and does it lock my data in?

PaliCAD is a lightweight, direct-modeling 3D CAD app, built on its own geometry kernel called Pali Ijo.

Sketch on a construction plane, extrude a solid, edit the faces and edges directly.

No parametric history tree to fight when you just need to change a shape.

It works on Windows, Mac, Linux, and iPad, and it is fully offline.

On iPad it is built for touch and Apple Pencil, plus keyboard and mouse.

What it does, in plain terms:

Sketch with lines, circles, rectangles, polygons, and splines, then extrude and refine.

Combine, subtract, and intersect solids, with fillets, chamfers, and hollowing.

Inspect faces and edges, run section analysis, and check what is actually inside the model.

It reads and writes the formats that matter for moving work along: STEP, STL, 3MF, and DXF.

Projects save as native .pali files, cross-platform.

Here is the part that matters most for construction and for AI work downstream:

Pali Ijo is a standalone Dart CAD kernel, boundary representation, mesh operations, measurements, and file interchange.

It is MIT licensed, and it can be used independently of the PaliCAD app and Flutter.

That is different from the app itself.

The app source is no longer in the public repo. The repo now carries the kernel source and project information.

The app is sold through Patreon and the iPad App Store, and the app license and branding are retained by the builder.

Do not mix those two up.

What the TPS REPORT - security JMAC-Secure-Cyber-Code-Review powered by https://github.com/JMacCyber/JMac-Secure-Code-Review review found:

The kernel code review came back with zero confirmed findings at the reviewed commit.

For local, offline use, the review rated it low risk.

Two hardening fixes were recommended before you feed it untrusted files: bounds-checking on 3MF ZIP handling, and validation on the .pali decoder.

And do not embed it in a network-facing service that parses user-uploaded CAD until those are in.

That is a fair, field-honest line.

Where it fits on a real job:

Early concept work, field problem-solving, and quick geometry checks, where a full BIM seat is overkill.

Teaching and workforce work, where a low-cost, offline tool lowers the barrier to entry.

Small to moderately complex designs. The builder says so himself, and I agree with that scope.

Where it does not fit, yet:

It is not a BIM replacement, and it is not a parametric production CAD system.

It is not the tool you run a whole project delivery on.

Pricing, as listed today:

iPad 1.0.4 is a one-time purchase, 6.99 USD.

Desktop 0.1.4 alpha, Windows, Mac, and Linux, is through Patreon, 8.99 CAD one-time for release builds, or 4.49 CAD a month for release plus beta builds.

An untested Android APK is available for sideload.

Models you make are yours, including for commercial use, with no added PaliCAD restriction on those models.

My take:

Open geometry plus standard formats is what makes downstream work possible, including AI work.

A model locked in a proprietary format helps nobody on the next step of the job.

A lightweight, offline tool with an open kernel you can actually inspect is worth knowing about, used inside its scope. This tool reminds me of the original SHAPR3D iPad application before they decided to become an ONSHAPE competitor. I would also recommend this to anyone wanting to create 3D Models for 3D Printing. PaliCAD is a great example of the Open CORE application model.

Not demos. Decisions.

Where would a tool like this actually earn its place on your jobs?

Early concept, field checks, or training?

Sources at the end.

https://github.com/braydennilsen/PaliCAD/tree/main

https://palicad.braydennilsen.com/

https://github.com/JMacCyber/JMac-Secure-Code-Review

Blog Post Written by Muse.AI MIA using

@Todd Sutton

Prompt Direction

Special Thanks to:

@Jobi Armstrong