01How Recon is built
Recon is two processes on your computer. The window you see is a desktop shell; next to it runs the engine, a local service that holds the geometry kernels and the checking code. The shell starts the engine when the app opens and stops it when the app closes; if the shell ever crashes, the engine notices and exits on its own.
The engine listens only on the loopback address (127.0.0.1) on a port chosen at start, and it requires a per-session token that the shell generates and passes to it. Another program on the same machine cannot talk to the engine without that token; nothing on your network can reach it at all.
02What is on your disk
Everything Recon keeps is under a .martensia folder in your Windows user profile:
- Jobs: the files you gave each run and the results it produced.
- Drawings cache: what was read and built from each drawing, keyed by the file's hash, so a rebuild with other parameters is free and offline.
- Settings: your preferences and the API key you entered.
The API key is stored in that settings file, readable by your Windows user. Protect it the way you protect the rest of your profile: a password on the account, and disk encryption (BitLocker) on a laptop. If the key leaks, revoke it in your Anthropic console and paste a new one; Recon keeps no other credential.
03What leaves, and how
Scan tools and Sheet → DXF never send anything. The AI tools send the drawing you chose to Anthropic's API, and nothing else, and only after you confirm the run.
For Drawing → 3D, Drawing ↔ STEP, Drawing + scan and a Batch, the engine sends to api.anthropic.com over TLS: the page image of the drawing, the text extracted from it, the instructions that tell the model what to produce, and, during the build, the intermediate results the model needs to correct itself (views of the model it wrote, the list of what is still missing). A STEP file you supplied for a check is not sent; the check runs locally and only its outcome goes back as text.
The request carries your API key, so the content is handled under your agreement with Anthropic. Under their commercial terms, API content is not used to train their models. MARTENSIA has no server in the path and never sees the content.
The app has no other network activity: no update check, no telemetry, no crash reporting. Version 0.1 does not phone home, and a future version that offers to will ask first and default to off.
04The build sandbox
Drawing → 3D works by having the AI model write a short script on an open CAD kernel, which the engine then runs to produce the solid. Code written by a model is treated as untrusted: it runs in a separate child process, started in Python's isolated mode so that it cannot pick up code from the working directory or your environment, with the kernel's libraries and nothing else of yours. The script ships with the result so that an engineer can read what was run.
05The installer
The early-access installer is not yet code-signed, which is why Windows SmartScreen asks once. Every build's SHA-256 is published in the release notes, and on the download page once downloads open, so you can confirm the file you have is the one we built. Signing is planned before general release.
06On-premise and API
The same engine can run on a Linux server inside your network, for a team that wants one installation or a system (a quoting site, a PLM, an ERP) that sends jobs over HTTP. In that mode every request must carry an API key made in Settings, webhooks are signed so your receiver can verify them, and the server's own outbound traffic is the same single path described above. A deployment where the AI model also stays inside the EU is on the roadmap; ask us if you need it.
07This website
martensia.com is a set of static pages served over HTTPS. It has no accounts, no forms that post to us (the contact form opens your own mail application), and no advertising or analytics trackers. The site serves its own fonts and loads nothing from a third party.
08Reporting a vulnerability
If you find a security problem in Recon or on this site, write to security@martensia.com. We acknowledge within 72 hours, keep you informed while we fix it, and credit you if you want. Please give us reasonable time to fix before publishing, and do not test against other people's installations or data. There is no bounty programme yet; there is gratitude, and a named thank-you in the release notes.