Work with 3D and CAD files in the browser: open STEP assemblies, fix DXF with AI, turn PDF drawings into 3D models and put tolerances inside the model.
CUTL opens full 3D STEP models right in the browser. Rotate, zoom, section and explode the assembly, and read everything the file already carries: no CAD seats, no exported screenshots, no converting to a neutral format first.

Invite your customer in to look at the same part with you. Pin comments, talk through the assembly live and agree on it in one place, with no endless email threads. When everyone agrees, push it straight to quoting.
Open any DXF, let AI clean the geometry, set bend lines and convert it to a folded 3D STEP model, without leaving the browser.

Your own DXF, a text description, a common shape or a photo of a part. All open in the same editor.
Bring your own DXF, describe the part and let AI draw it, start from a common shape, or photograph a part on the shop floor. Every route ends in the same editor, and every drawing in it can be converted to a folded 3D model without leaving the part editor.
Each bend has its own angle, direction and inner radius, calculated from material, thickness and K-factor.
Draw bend lines where the part folds and each one carries its own angle, direction and inner radius. The fold is calculated from the sheet: the part's material and thickness, its K-factor or an explicit bend deduction per bend. Convert, and the blank is folded along those lines into a solid you can inspect. A part with no bend lines is extruded to its sheet thickness with the holes cut through, which is all a flat laser part needs.
Bend lines that do not cross the part, angles outside 10° to 170° and crossing folds are blocked in the editor, not on the press brake.
A bend line that does not fully cross the part turns red and blocks the conversion, an angle outside 10° to 170° is rejected, and crossing folds are refused with the reason. You find out in the editor, in seconds, rather than on the press brake.
Upload a PDF drawing and get a 3D STEP model back, usually in 10 to 30 minutes. No tracing and no setup. Close the page if you like: we email you if we need you.

Finds the views, measures the outline and holes, reads dimensions and fold lines. Units, scale and projection are detected for you.
The conversion finds the views and works out how they relate, measures the outline and the holes, reads the dimensions and the fold lines, then builds the solid from a fold recipe. Units, scale and projection are detected from the drawing itself. If you already know them, declare them up front and skip the guesswork.
If a drawing is unclear, the run pauses and asks one specific question. Answer in the browser and it carries on.
When a drawing is genuinely unclear, the run stops and asks one specific question rather than handing you a wrong model: ambiguous units, a missing scale, two section views that contradict each other, unreadable fold lines, an unproven thickness. You answer in the browser and the run continues where it paused. Every reading it made is there to inspect alongside the drawing before you approve it.
Ready to view, nest, price and quote, and to enrich with PMI.
The result lands in your STEP library, ready to view, nest, price and quote, and to enrich with PMI. A drawing nobody can read stays a question rather than becoming a bad part.
Put GD&T, dimensions, datums, finishes and certificates into the STEP file itself, readable by the next machine and the next supplier. Add them by hand or import them from a spreadsheet, a QIF file or the drawing PDF.
PMI is for the team that owns the model. Invited reviewers see comments and the model, not the PMI panel.
ISO 1101 or ASME Y14.5, with 31 rules enforced before a frame can be added. Mark criticality per requirement.
Pick the characteristic, the tolerance zone and its form, the datums with their modifiers, a composite frame's lower segments, and whether it applies to one face, a pattern of features, the whole part or every instance of it. Mark what matters most with a criticality level and the designator your customer's inspection report is read against. Set the drawing standard once per part, ISO 1101 or ASME Y14.5 with its general tolerance class, and every frame is checked against that standard's rules as you type. A form tolerance cannot reference a datum, and the panel says so in words instead of letting a bad callout reach the file.
From a spreadsheet, a QIF file or the drawing PDF. Accept, edit or reject each row, with an audit trail.
Point it at a spreadsheet, a QIF file or the drawing PDF and each requirement becomes a row to accept, re-place, edit or reject. The review runs in rounds, one decision covering every instance of a part, with an append-only, hash-linked record of who decided what and when. That is the evidence an audit asks for, produced as a by-product of the work.
Enriched STEP, a QIF inspection program for PC-DMIS, Calypso or Verisurf, a ballooned drawing and an inspection report.
Saving writes a new version of the model and reports, requirement by requirement, what happened: written as semantic PMI, drawn as a callout, or refused with the reason. You stay on the version you were reading until you choose to move. Out come an enriched STEP model, a QIF inspection program for PC-DMIS, Calypso or Verisurf, a ballooned drawing and an inspection report: one requirement set in the four forms the supply chain asks for.
Give every part and sub-assembly you make a route: the ordered operations that turn a blank into the finished part. CUTL adds cutting and bending by itself, you add the rest from your own operations and machines, and a technologist approves it. The route feeds the price, the lead time, your ERP and the route card for the shop floor.
Click faces of the part and add them to the operation that works them. A steps strip shows the part as it grows.
Every line of the route can point at the faces it works on: the holes for drilling, the contour for cutting. Holes already in the part's PMI come ready to add in one click. A strip under the model walks the route step by step and shows the part as it is at each one, with the faces being worked in orange. Copy a route from another position or apply one of your templates, and reorder lines by dragging.
Hours add up per equipment type for the whole order, and Ready in estimates the working days, outside services included.
Times come from your operations dictionary, typed or worked out from the part's geometry with a formula such as 0.6 × holes. Rates come from the machine or the equipment type, so every line has a cost, and outside services such as galvanising carry a vendor, a price and a lead time. Ready in takes the longest equipment queue, from each type's hours per week, plus the longest outside-service lead time. It is an estimate, not a shop schedule.
A technologist approves and freezes the route. Export to your ERP as JSON or XML, or print route cards for the shop.
Technologists keep your standard routes as templates and apply them by rule to many positions at once. Approving freezes the operations, times and faces, while rates stay live. The ERP export carries the multi-level bill of materials, the routes, blanks and costing, with your ERP codes. The route card PDF comes as a shop traveller or a GOST 3.1118 card, with a picture of the model at every step.
Connect Claude, ChatGPT, Gemini or Cursor to CUTL over MCP and say what you need in plain words. The assistant opens STEP models, quotes parts and assemblies, reads routes, adds PMI and builds documents for you, as you and with your role's rights. Everything it does shows up in CUTL straight away.
Quote perforated-tube.step for 50 pieces and tell me when it can be ready.
Done: 50 pieces quoted in CUTL. Ready in ~6 working days, set by galvanising.
Core, STEP and MBD, Assemblies and documents, and Setup. Connect only the ones you use.
Each toolset has its own server address and is added as its own connector. Core covers projects, quotes, production and nesting. STEP and MBD covers reviews, comments, PMI, inspection documents, DXF to STEP and PDF to STEP. Assemblies and documents covers assembly pricing, quantity breaks, routes, route cards and ERP export. Setup covers machines, materials and customers. An assistant picks tools more reliably from a short list, so add only what you need.
Paste a token into Claude Code, Cursor or Gemini CLI, or sign in from Claude.ai, ChatGPT or Gemini Enterprise.
A token works with every toolset and expires after 30, 90 or 365 days, or never. Signing in connects one toolset at a time and ends when you press Disconnect in CUTL or after 30 days without use. Either way the assistant acts as you: it can read and change exactly what your role allows, no more, and you revoke it in Settings, Integrations.
Assistants spend coins only within the limits you set, and their work lands in CUTL as ordinary projects and quotes.
Set the assistant coin limits on the Integrations tab so an assistant cannot run down your balance. What it creates are ordinary projects, parts, quotes and production tasks that your team sees and can change in the web app, so nothing lives only in a chat.
The Documents tab of the STEP viewer writes assembly manuals, part and product passports and parts lists from the model. Tables, facts and pictures stay tied to it, so when the model changes the document shows exactly which values moved. Export to PDF or editable DOCX with your title block.
Looking at a file needs no account. Create a free one when you want to keep it, share it with a client or use the other tools.