Common-line cutting and kerf, done properly

Less cutting on the edges that face each other.

Tick Common-line cutting on the job. Lapas joins copies of a part along their straight edges, exactly one kerf apart. The machine cuts down the middle of that gap once, and both parts come out at drawn size there.

Only real shared edges sit that close. Every other gap keeps the job's full part spacing, so an edge that is not shared is never nested closer than your process allows. And a layout on fewer sheets always wins over one with more shared edges.

Shared edges are drawn in teal on the sheet. A badge on the result counts them, with the length of cut saved.

The export says it again: how many shared edges are cut once and how much cut that saves. Set a cut rate for the material and it also tells you about how much cutting time.

Works from a 0.1 mm kerf, so on lasers too. Copies are joined in clusters of 2 x 2 unless you set a larger size: a bigger cluster shares more edges, but leaves longer strips of plate that can move under heat.

Pick the machine on the job, and it brings its spacing, holds and kerf with it.

Settings has a new page, My machines. Setting one up is a short walk-through: one setting per step, each with a picture of what it does on the plate. Each step starts from the usual numbers for that process, so you only change what is different on your machine.

Start from a template for your controller. Or upload a program your machine already runs, as G-code, a CypCut DXF or PLT: Lapas shows which machine it looks like and why, and nothing changes until you pick. A kerf table comes in from a spreadsheet or a CSV.

Then a job only has to pick the machine. A new machine spaces parts by the usual rule for its process, and you can change it: on plasma the larger of 3 x kerf and the plate thickness, on a laser at least the plate thickness, on a router the bit. The machine also brings its holds (micro-joints on a laser or plasma, tabs or onion skin on a router) and its kerf compensation.

Machine not listed? Send us a program it runs from the setup page. Machine programs are new in Lapas: run the first one on your own table before production.

A path that cuts into a part is caught before it reaches the table.

Before you download, Lapas replays the G-code or PLT it wrote against your parts. It looks for a cut through a part, an edge left uncut, a joint cut through, or a cut crossing one already made.

If one part fails, that part is left out of the program and listed with the reason. Every other part on the sheet is cut as normal.

The export status says it straight: All checks passed, or how many things are left to review.

Clean part edges, and parts that stay put until you take them out.

Pierces are kept off every part edge, and a second pierce moves out into scrap. Where there is no room, the export says so.

Lead-ins are fitted to the scrap around the compensated outline. A lead that would reach a neighbouring part is shortened, and the export tells you how many were.

New option: micro-joints, and tabs or onion skin, to hold parts in the sheet. The joint length follows the plate thickness, and a joint is never shorter than two kerfs, so the beam cannot eat it mid-cut.

Holes are cut before outlines, as before. On machine outputs that can mark, engrave-layer marks now run before any cut.

One request from your ERP or quoting tool: drawings in, sheets and machine files out.

The same nesting as the app, over plain HTTP. Send your DXF, SVG or DWG drawings and the sheets you have in the request itself, and ask for the files you want: DXF, SVG, G-code for one of the machine posts, PLT, or the PDF report. Ask it to wait, and a quick nest comes back finished in the same call, ready to quote from.

Longer jobs run in the background and Lapas calls your system back with a signed webhook when they finish. A free estimate tells you the price before anything runs. It runs Lapas Core with the same checks as the app: a layout that fails them is never returned, and a nest that fails is not charged.

Test keys run the real engine and return real files, and are never charged. They take up to 100 parts and 30 seconds a nest, enough to try it on your own drawings, then you switch to a live key.

Everything about it, for your developer or your AI assistant, is on the Lapas API page. Keys are in the developer console at app.lapas.io/console; the reference, with a request you can try in the browser, is at app.lapas.io/docs.