Short answer
Cloud slicing means preparing print files for every printer in one place, with one slicer and saved settings. Which file was sliced with which settings no longer disappears into one person's laptop, and printers of different brands go through the same process. AMENT Hive runs the open-source OrcaSlicer, unmodified, in the cloud; saved setting sets, colour mapping, the prime tower, a plate editor and a versioned file catalogue are part of the same flow.
Key takeaways
- Slicing should happen in a shared, recorded place, not on one person's computer.
- One slicer brings the same settings language and the same record-keeping to every brand.
- Mapping a file's colours to the printer's slots prevents the most common multi-colour mistake.
- The original file should never change; layouts and new versions are stored separately.
- AI setting suggestions should only fill in the form; slicing and sending stay a person's decision.
Why should a print farm slice in one central place?
With one printer, a slicer is a personal tool: you install it on your own computer and tune your settings over time. On a farm, slicing is a production step, and production steps run on personal tools drift apart.
- A slicer per brand: one program for the Bambu printers, another for Creality, a third for the Klipper machine. Each names and defaults its settings differently.
- Settings on one computer: the PETG profile that works lives on the old laptop in the workshop. If that laptop dies, so does the profile.
- Versions tracked by file name: "cover_final.3mf", "cover_final_really.3mf", "cover_v3_new.gcode". Nobody is sure which one was printed.
- Re-slicing for another printer: printing a file prepared for a P1S on a K2 means opening the program and setting everything up again.
- Colour and slot confusion: which slot on the printer does the file's fourth colour land on? A wrong mapping means a whole plate in the wrong colour.
What these problems share is that knowledge is tied to one person or one computer. When the owner is ill, an operator changes or a new printer model arrives, what you need to print the same product at the same quality is suddenly out of reach. The risk grows with the farm, because files and printers multiply while the number of people carrying the knowledge usually stays the same.
Central slicing does not patch these one by one; it removes the cause. File, settings and result sit in the same place, with who sliced what and when. For the settings themselves, see our print settings guide.
One slicer for every brand: OrcaSlicer in the cloud
The cloud slicer in AMENT Hive is OrcaSlicer. OrcaSlicer is open source and distributed under the GNU AGPL v3 licence. Hive runs it on its own servers, unmodified and as a separate process; fixes to printer profiles are made in the settings data Hive passes in, never inside the program.
Thanks to OrcaSlicer's own printer profiles, the same file can be sliced for your Bambu Lab, Creality, Snapmaker or Klipper printers. When Hive recognises a printer in your farm it suggests the matching profile; when it cannot, it asks you to pick one. There is nothing to install: slicing starts in the browser and finishes in the cloud.
- Plate by plate: each plate becomes its own print-ready file for the printer it is going to, with a time and gram estimate.
- The right format: G-code for Klipper printers, and the .gcode.3mf package Bambu printers expect.
- Thumbnails: where the project contains a picture of the plate, the thumbnails shown on the printer's screen are made from it, in the sizes that printer wants.
- 3MF projects: Hive slices Bambu Studio and OrcaSlicer 3MF projects. If all you have is an STL, place it into a 3MF project first; the full OrcaSlicer in the browser can do that too.
The same file is never sliced twice
If the same file, layout, printer, settings and slicer version were sliced before, Hive says so and reuses the earlier result: already sliced with these settings, no waiting. You can still force a fresh slice. It shortens the queue and means the same product prints from exactly the same G-code every time.
Setting sets, colour mapping and the prime tower
In the slicing panel you choose the printer first, then the process profile. The settings people change most sit in a simple form: layer height, first layer, wall loops, top and bottom layers, infill density and pattern, supports and overhang angle, brim, prime tower, seam position and ironing. If you need a deeper OrcaSlicer setting, add it line by line as key = value.
- Keep the file's own settings: changes you made while preparing the project can be kept, with the form's changes applied on top.
- Saved setting sets: name and save a set such as "PETG strong parts" with its process profile and changed settings, and apply it in one click next time.
Mapping the file's colours to the printer's slots
In a multi-colour project, each colour in the file must land on a slot on the printer. Hive reads the material and colour loaded in Bambu AMS units, Creality CFS units and Snapmaker U1 heads straight from the printer. For printers that do not report it, you enter the loaded filament by hand. Mapping looks at material first, then at the nearest colour.
- If a file colour and the filament in its slot are different materials, that is shown plainly; same material in another colour shows as a warning.
- If the file has more colours than the printer has loaded slots, you are told which colours share a slot and will print in the same filament.
- On a printer that changes filament by hand, you are warned in advance that the print will pause at every colour change.
The prime tower is switched on or off in the form, and moved by dragging it in the plate editor. For the basics of colour printing, see our post on multi-colour 3D printing.
The plate editor: split, duplicate, 2D and 3D views
A project arrives with all its parts on one plate, but you only want to print the left covers. Or you want to take a four-copy plate up to twelve. You should not have to open a desktop slicer and re-save the file to do that.
- Split: "One part per plate" gives each part on a plate its own plate, named after the part.
- Duplicate, copy, paste: duplicate parts and move them to other plates; name plates, add them or remove them.
- Arrange and smart arrange: lay parts out neatly; smart arrange packs tighter with offset rows and 90° turns and is never worse than a plain arrange.
- Fill to max: adds as many copies of the selected part as fit into the space left on the plate.
- 2D and 3D: you move and turn parts in the 2D view; the 3D view is for looking around and selecting.
Working out the most units per plate for each printer model is covered in our plate planning guide.
A file catalogue with versions: 3MF, STL and G-code
Hive's catalogue keeps 3MF, STL and G-code files with their versions. Uploading a file starts a project; uploading a new file to the same project continues it as v2, v3 and so on. If you upload exactly the same file again, no new version is created and it is not stored twice.
| Source | When | Note |
|---|---|---|
| Upload | You upload a new file to the project | Earlier versions stay as they are |
| Full slicer | You save in OrcaSlicer in the browser | The project comes back as a new version |
| Layout | You download a plate layout and upload it back | Hive knows which layout it came from |
| Duplicate | You copy the project | Identical content is stored once |
Files can be renamed, annotated and duplicated. Product profiles show when a newer version exists but never switch to it on their own; the person who approves production decides which file is used. Storage clean-up works the same way: unused old print-ready files are listed first and deleted only when you confirm. Nothing is cleaned up automatically.
The full OrcaSlicer in your browser (paid module)
For the cases where the form is not enough, Hive offers a paid module that opens the complete OrcaSlicer in the cloud, in a browser tab. Paint supports, cut a part, build a new 3MF project; when you save, the project returns to Hive as a new version and earlier versions stay untouched. The module is enabled per farm.
Cloud slicer or desktop slicer?
Cloud slicing does not mean throwing away your desktop slicer. Each is good at different work, and most farms use both. The difference is where design work ends and production work begins.
| Job | Desktop slicer | Hive cloud slicing |
|---|---|---|
| Setting up a new product's project | Comfortable: painting, cutting, supports | Possible with the full OrcaSlicer module |
| Preparing an approved product for another printer | By hand, every time | Pick the printer; colours are mapped |
| Printing the same file again and again | A separate file on each computer | The earlier result is reused |
| Who sliced what, with which settings? | Unknown | Recorded, with the version |
A practical split looks like this: whoever designs a new product sets up the project in the program they know and uploads it to the catalogue as a 3MF. Everything after that, adapting it to another printer, filling the plate, mapping colours and printing it again, happens in Hive. Design keeps its freedom and production keeps its repeatability.
AI setting suggestions: nothing changes until you press Apply
If a product keeps lifting off the plate on a particular printer, or the first layer keeps causing trouble, a second pair of eyes on the settings helps. In Hive that second pair of eyes is an optional AI suggestion, with tightly drawn limits.
- Off by default. The owner switches it on.
- Only on request. It runs when an owner or production manager presses "Get suggestions" in the slicing panel.
- Looks at real data. It considers the file's facts, the chosen profiles, the settings you changed, and this farm's failed prints for that project and printer over the last 90 days.
- Limited to allowed settings. Every suggestion is re-checked against an allow-list; temperatures are not on it, numbers are kept within sensible ranges and layer height is capped by the nozzle. Anything outside the list is dropped, and you are told.
- Apply only fills the form. Nothing is sliced, saved or sent to a printer on its own. You check the form, then slice.
- No repeat cost. If the same question is asked again within 24 hours, the earlier answer is reused.
Sending the sliced file to a printer is a separate step and is still being validated in the field (🧪); we cover it in our post on remote printer control. If you would like to try cloud slicing with your own files, start a 14-day free trial of Hive.
Frequently asked questions
Which slicer does Hive use?
Hive uses OrcaSlicer in the cloud. OrcaSlicer is open source and distributed under the GNU AGPL v3 licence; Hive runs it unmodified, as a separate process.
Can I slice an STL directly?
The catalogue stores STL files, but Hive's cloud slicer slices 3MF projects. Place the STL into a 3MF project first, in Bambu Studio, OrcaSlicer or Hive's full OrcaSlicer module, then upload that.
Can I slice the same file for printers of different brands?
Yes. You choose the target printer when slicing; Hive suggests the matching OrcaSlicer profile, maps the colours to that printer's slots and prepares each plate as its own file for that printer.
Will editing plates change my original file?
No. The original file never changes; a layout is a separate recipe Hive applies when slicing or downloading. You can download the layout as a .3mf if you want it.
Do AI setting suggestions change my settings on their own?
No. The feature is off by default and only runs when you ask. Suggestions fill the form only when you press Apply; slicing, saving and sending are always your steps. Temperature settings are outside what it may suggest.