Engineering factory.

00 — One mark, three states

Tesryn, orchestration, Aximyr.

The same five parts, rearranged. The orange one is the keystone that locks the T, the segment that closes the O, and the datum every number is measured from in the A.

01 — How it works

From a sentence to a checked design.

Describe the job. Aximyr chooses the parts, assembles them from the makers’ own models, designs the parts nobody sells, checks the lot and hands you the package.

1. Describe

   Say what you are building, in your own words, or attach the RFQ, the drawing or the customer’s STEP file. Aximyr reads it into fields you can see and correct, and asks only the questions that decide the design.

2. Design

   Sketch a part to exact dimensions and extrude it, or make it from parameters. The parts nobody sells (adapter plates, fingers, fixtures, pedestals) are designed to fit what they join.

3. Assemble

   Bought parts arrive as their makers’ own models. They join by their real interfaces: an ISO 9409 flange to a flange, a bolt pattern to its holes.

4. Check

   Payload, grip, air supply, interfaces, interference, gravity, and how each part is held. Every check answers PASS, FAIL, UNKNOWN or NOT CHECKED, with the quote it rests on.

5. Deliver

   A bill of materials, drawings, assembly instructions, a layout and a report that cites its sources, bound to one revision. Change a requirement and Aximyr marks what has gone stale.

02 — Honest unknowns

Four answers, never a guess.

Most engineering software hands you numbers; the question is which of them you can stand behind. In Aximyr every check answers one of four ways, and shows the quote it rests on.

• Pass

  It holds, on the maker’s own data or a calculation from it.

• Fail

  It doesn’t, and here are the figure and the limit.

• Unknown

  Nothing proves it either way yet, and here is what would.

• Not checked

  No check covers it, or it wasn’t run.

A model’s guess never becomes a PASS. Neither does a default. A value nobody stated is not zero: the check tries it at its best case to find a FAIL, and if none appears it stays UNKNOWN and names what is missing.

03 — Every number has a source

Every figure traced to its page.

One request — a robot cell that picks 5 kg parts inside a safety fence — run through Aximyr from requirements to a buy list. These are the figures from that run:

• 60

  configurations worked through, each one checked

• 24

  engineering checks passed on the one it chose

• 36

  mating pairs checked in CAD, none overlapping

• 5 buy-list lines, each quoting its source page.
• 11 values it refused to invent, and named instead.

AI helps the work along, but it never supplies a number a decision depends on. Every value comes from the manufacturer’s own documentation, a calculation from it, or is flagged as unknown for an engineer to resolve.

The first application is robotic palletizing. From a request, Aximyr proposes the cell, checks payload, reach, grip and fit against the makers’ data, lays it out, and writes the robot program for an engineer to review. It is preliminary engineering, and partial today: one cell type, demonstrated on real manufacturer data, with what it checked and what stays unknown written into the package. Passing its checks does not certify a design or replace an engineer’s review.

04 — What Aximyr is made of

Switch on the modules a project needs.

Each one is a part of Aximyr, drawn from the same datum. Underneath every module sit the same checks, the same evidence and the same record.

• 

  Industrial cell

  From a sentence to a checked robot cell.

  Describe the job in plain words. Aximyr reads it into a requirement, picks the robot, gripper and coupling against their makers’ data, designs the adapter plate between them, guards the cell and checks the payload against the robot maker’s own load diagram.

• 

  CAD

  Draw it to dimension. Build it from there.

  Sketch a profile with holes and pockets to exact dimensions, or read one from a DXF, and extrude it. A maker’s STEP comes in as a part of the project, and every hole is checked on the model it bolts to.

• 

  CAM

  From the model to the machine’s file.

  Make what you designed: STL, 3MF and OBJ for printing, slicing to G-code, laser G-code with kerf compensation, nesting on a sheet, and 2.5D milling.

• 

  FEM

  Physics you can check against the textbook.

  Structural, thermal, fluid and magnetostatic studies on a part. Each solver is held to a closed-form answer before its results are trusted.

• 

  Magnetic tweezers

  Force on a bead, sized from first principles.

  The research process for magnetic tweezers: requirements, the magnet’s architecture, sizing from cited formulas, verification by FEM, the parts, and the BOM.

• 

  Visualizer

  Show it the way it will look.

  Colours, finishes, the light and the floor for the whole system, and ray-traced renders to save as pictures. Presentation only: no check reads it.

05 — Proof, not adjectives

Measured, not promised.

• 0

  unsupported PASS across 31 frozen requests run with no model: 21 feasible, 7 invalid, 3 incomplete, all answered as expected

• 730

  catalogue quotes re-read by the tests, each found on the cited page of the maker’s own document

• 114 ms

  to place 3 parts with every network call refused; 26 checks in 39 ms, the BOM in 38 ms, five runs ending on the same design digest

• Held to the textbook. A cantilever’s tip deflection lands within 0.5 % of Timoshenko’s; a solenoid’s field within 0.2 % of the closed form.
• 253 tools, open to agents. Each has a card saying what it answers and how it fails, and outside agents reach them over MCP.
• Over 10,000 automated tests. Counted on the build of October 2026.

06 — Around Aximyr

Engineering fast enough to change what you’d attempt.

When engineering moves faster, more ideas become worth pursuing.

Tesryn builds engineering automation software, and Aximyr is what you buy. Around it, the same engineers do the work that makes a package land: connecting it to the systems you already run, a second opinion on an architecture or a quote, and building alongside a partner who brings the domain. A written scope and price before work starts, a working result in week one, and everything handed over to you.

• IntegrationAximyr’s packages into the systems you already run — ERP, CRM, the equipment on the floor — through APIs, webhooks and event streams.
• ConsultingAn architecture decision settled, a stalled project recovered, a system or a quote checked, a team brought up to speed on building with AI.
• PartneringYou bring the problem, the domain and the users; we bring the engineering. Terms in writing before work starts.