From a drawing or from existing G-code · beta
Draw a part or load G-code from the program you already use. IDS WebCAM computes the run with your router's accelerations: it shows how long the job will take and where the cutter cuts or rubs, and hands back a file with feeds matched to your machine.
The feed rate in your file is often a leftover, not a decision. Your CAM computes the geometry and your controller handles the motion. In between, nobody checks whether the cutter is actually cutting, or whether the machine could go faster. That's how you get three things every workshop knows:
The feed rate came over from the settings of an older, smaller machine. The new one could run four times faster, but nobody touched it, because nobody knows where the limit is.
Across 61 production files, every cutter at F2000 was running 1.3–4× below its minimum chipload. It rubs instead of cutting, heats up and dulls faster.
Before a corner, the controller rightly slows down. The spindle speed stays the same, so the chip gets thin and the cutter starts to rub. You see it as burn marks in MDF and shorter tool life.
On a gantry router, a 90° corner costs 0.109 s of braking and accelerating. With thousands of corners in a program, that adds up to minutes with the cutter outside its window.
CAM divides path length by feed rate. On short segments the machine never gets up to speed, so the real cycle time is longer and the job is quoted too low.
On a 3D decorative panel, a ⌀6 mm ball-nose with an 8,000 mm/min ceiling averaged 1,513 mm/min and took 62% of the cycle time.
A model of acceleration and braking predicts what your controller will do: how fast the machine is really moving at every point of the toolpath. That gives you three views of the same file:
The colour of the path shows how fast the machine is really moving. You see at a glance where the file leaves performance on the table.
Where the machine brakes, where it accelerates, and which point of the path is the slowest. A map of every place where the gantry gets a jolt.
Ochre marks where the chip gets too thin and the cutter rubs instead of cutting. The report shows what share of time each tool spends there.
We check the model with a stopwatch on real runs. Where a number comes from a calculation, we say so.
A block with 99 corners ran on a gantry router in 45.88 s. The model predicted 45.94 s. No constant was tuned to hit that result.
Measurement M14 · Certus router, PikoCNC controller · test block, real run
Raising the ceiling from F2000 to 8,000 puts every calculated cutter inside its chipload window, with no change to spindle speed.
Analysis A1 · 61 production files · calculation, no test cut
A 17.9 MB file (2,500 mm decorative panel) is processed in seconds. The 3D preview rotates smoothly at 156 frames per second.
M20, M21 · real file · one computer, one browser
You start from a drawing or from G-code from the program you already use. IDS WebCAM computes the run and returns a program with feeds matched to your machine. In a file from another program, the toolpath stays the same.
Draw a part or import a DXF. Or drag onto the page the file from your CAM, exactly as it goes to the machine.
A machine profile (acceleration, max feed) and a tool library with chipload windows for 7 materials.
Feed, dynamics, chipload, and cycle time broken down by tool.
A program with feeds matched to your machine. Optionally, line segments merged into G2/G3 arcs.
Geometry, bit for bit. Coordinates stay untouched, and every release passes a test that checks it. Only feed rates, spindle speeds and (if you want) arc output change.
Cabinet doors, decorative panels, letters, light boxes. Batch work, where every minute per part gets multiplied by the quantity.
A machine whose stiffness depends on where the tool is. That's where a dynamics model pays off most.
Your customers' programs are your know-how. Everything is computed in the browser, so recalculating a file never sends it anywhere. Only what you decide to save reaches our server.
You can always export your machine profile and tool library to a file, even if you stop using the service.
We're not competing on the number of strategies. Every new strategy computes the geometry and hands it to the same planner that already improves your files today.
Pilot · autumn 2026
We built this on our own machine. Now we want to compare it with yours. The pilot is free: you get a profile of your machine and a review of your files, and we learn how other gantries behave.
Which machine, which controller, which CAM your files come from, and what bothers you most. Don't send your file. Run it through IDS WebCAM yourself, in your browser.
Your controller's planner (look-ahead, S-curve acceleration) keeps the machine within its acceleration limits. It can only slow down below the feed rate in the program. It won't raise an F2000 left over from an old machine, and it doesn't know which cutter you're using or what you're cutting.
IDS WebCAM doesn't replace your controller's planner. It predicts it. So you see chipload and cycle time before you press Start, and you can raise the feed ceiling where the cutter will benefit.
The dynamics view shows where the machine brakes and accelerates hard, which is where to look for them. We're currently testing on our machine whether a local feed reduction reduces them better than controller settings alone. We'll publish the result here.
No. You can draw a part in your browser, with contour, pocket, facing, drilling, chamfer and line engraving, and get a program with feeds matched to your machine. You can also load G-code from the program you already use.
In a file from another program, no. Coordinates stay bit for bit, and a test checks it on every release. Feed rates change, and optionally spindle speeds and arc output (G2/G3, 0.01 mm tolerance, off by default). A toolpath drawn in IDS WebCAM is created in the program right away and goes through the same planner.
You don't have to. Everything is computed in your browser, so recalculating a file never sends it anywhere. The account we are testing carries your machine profile and tools between computers. You'll also be able to keep files there if you want to. It's your choice for each file, not ours.
From the machine profile: axis acceleration, maximum feed rate, and cornering behaviour. You start with the values from your controller. Comparing the predicted cycle time with a stopwatch tells you whether the profile is right. On long 3D files with very short segments, the model still underestimates time, and we're working on it.
Not yet. Today it reads metric G-code (G21). Inch support is on the roadmap. Until then, post your files in millimetres.
IDS WebCAM is free today. We'll announce CAM pricing before the end of the beta, to pilot participants first. You can always export your machine profile and tools to a file.