Skip to content
Public beta · free during beta

Your production hub for laser engravers and CNC machines.

GRBL Server ingests SVG, PNG, JPG, DXF, and G-code from local folders, databases, or S3, processes them through reusable workflows, and sends jobs to any GRBL, GRBL-ESP32, Marlin, Smoothieware or Klipper machine on your network.

GRBL over USB serial · ESP32/FluidNC over Wi-Fi · Klipper, Smoothie & Marlin over TCP. One server, every machine on your shop's network.

Diagram: SVG, PNG, JPG, JPEG, DXF and raw G-code files arrive from a database, Amazon S3, or a local folder. GRBL Server processes them through file conversion, workflows, presets, macros, sequences, interfaces, grids and clipping, then sends jobs to diode lasers, CO2 lasers and CNC routers running GRBL, Klipper or Marlin.
Files in. Sources connect. Workflows process. Machines run.

More than a sender.

Most laser engraving software is either a design tool or a one-machine sender. GRBL Server is the production layer in between: file sources, reusable workflows, presets, and a fleet of laser engravers and CNC machines on your network.

vs LightBurn

LightBurn focuses on designing and sending a single job to a single machine. GRBL Server skips design and focuses on reusable, multi-machine production.

vs LaserGRBL

LaserGRBL is a simple sender/converter. GRBL Server adds workflows, mediators, grids, clipping, presets, and fleet management on top.

Built around how production actually works.

A small set of building blocks that compose into reusable workflows.

Multi-machine fleet

Connect GRBL, GRBL-ESP32/FluidNC, Marlin, Smoothieware and Klipper controllers over USB serial, Wi-Fi or TCP. Drive a fleet of laser engravers and CNC routers from a single server.

Visual workflow editor

Build reusable production pipelines with nodes: file sources, mediators, interfaces, presets, grids. Edit once, run forever.

Grid-based batch jobs

Tile a design across the working area or assemble different files into a single production batch with one node.

SVG path clipping & cropping

Constrain any job to an SVG d path or a rectangular bound. Useful for material-shaped batches.

Flexible file sources

Pull SVG and image files from local folders, databases (parameterized SQL), or S3-style storage. Production data, not just local files.

Presets & interfaces

Save reusable machine, power, speed, and pass settings. Apply them across jobs without re-entering parameters every time.

Pre-visualizer

See exactly where the job will land on the working area before sending — with snap-to-grid alignment and the machine's bed as backdrop.

Real-time job control

Pause, resume, and kill running jobs without disconnecting. State stays on the server, not on the device that submitted the job.

Local-network access

Run it on the workshop computer; open it from any phone, tablet, or laptop on the same Wi-Fi — by IP address or the grblserver.local shortcut. No cloud account required.
Reusable workflows

Wire it once. Run it every shift.

A workflow is a graph of nodes: where files come from, how they're processed, how they're arranged into a grid, what clipping applies, which interface and laser engraver receives the job.

  • 1 Define file sources (local folder, database mediator, S3).
  • 2 Pick an interface (the engine parameters — power, speed, passes; handles vector and raster in one profile).
  • 3 Arrange into a grid and apply clipping if needed.
  • 4 Target a machine endpoint — laser engraver or CNC, over serial, Wi-Fi or TCP — and run.
GRBL Server workflows list with production_batch_a and acrylic_run_b workflows, each with Open, Compile, Run and Delete actions
GRBL Server machines administration showing four configured machines: laser_A (COM4 serial), cutter_B (websocket), engraver_C (serial), mark_D (websocket)
Multi-machine

One server, every machine on the network.

Connect GRBL, GRBL-ESP32/FluidNC, Marlin, Smoothieware and Klipper controllers over USB serial, Wi-Fi or TCP. Each machine appears as a named endpoint with its own working area and idle/active state.

  • · USB serial for GRBL, Marlin and Smoothieware boards.
  • · Wi-Fi WebSocket for GRBL32 / ESP32 / FluidNC controllers.
  • · TCP for Smoothieware, Klipper (Moonraker) and Marlin over the network.
  • · Per-machine working area, description and identifier.
  • · Connect / disconnect from any device on the network.
Files · grids · clipping

From a folder of SVGs to a full sheet of jobs.

Load files from a local folder, an external database, or an S3 bucket. Multiply them by the number of cells you need, arrange them in a grid across the working area, and clip the result to the material you've actually got on the bed.

  • · Filter files by prefix, suffix, extension, recursion.
  • · Multiplier per file for batch quantities.
  • · Grid tiling with configurable rows, columns, gap.
  • · SVG-path clipping using d attributes.
  • · Rectangular cropping for sheets and offcuts.
GRBL Server local folder file browser showing SVG files (order_42_keychain, order_43_tag, order_44_coaster) ready to be configured as jobs
GRBL Server presets list with plywood_3mm_engrave, acrylic_5mm_cut, steel_mark_basic and cardboard_test presets
Presets & interfaces

Save the dial-in once. Reuse it for every order.

A preset bundles together a machine, an interface (power, speed, passes), clipping, and the pre-visualizer layout. Once you've found settings that work for a material, save them as a preset and apply them in one click on future jobs.

  • · Per-material presets: plywood_3mm_engrave, acrylic_5mm_cut, ...
  • · Interfaces store the engine parameters — one profile covers vector, raster, and SVGs that combine both.
  • · Sequences wrap each job with start / end G-code.
  • · Macros for reusable controller commands.
Public beta

GRBL Server is free during beta.

Early adopters will keep a permanently discounted price when paid plans are introduced.

Built by one developer.

Hi, I'm George Domingo Herrezuelo. I built GRBL Server to simplify modular GRBL laser engraving workflows, especially for multi-engraver and reusable batch setups. The project is developed independently and shaped by beta feedback.

Read more about the project →