Skip to content

AMENT Hive guide: AI print farm management software

A full walk through AMENT Hive, AI-assisted production software for 3D print farms: what it does, how it works, how to set it up and what it does not do yet.

AMENT Research TeamPublished 23 min read

Upload to printer

Short answer

AMENT Hive is AI-assisted production software for 3D print farms. It gathers Trendyol, ikas and Shopify orders into one queue, plans production, slices files in the cloud with OrcaSlicer and shows Bambu Lab, Creality, Snapmaker and Klipper printers on one screen. A Farm Connector at the farm talks to printers on the local network and connects outwards only to Hive. The AI prepares work but never starts a print on its own: upload and start are two separate human confirmations. Hive has a 14-day free trial and published pricing, and sending to printers is being validated in the field.

Key takeaways

  • Hive keeps the whole chain in one place: orders, plan, files, slicing, printers, filament and quality.
  • The Farm Connector talks to printers on the local network and only connects outwards; your printers are never exposed to the internet.
  • The AI prepares, a person approves: upload and start are separate confirmations, and remote commands are never available to the assistant.
  • Sending to printers, remote control and calibration are live but still being validated on real printers.
  • First setup takes about 30–45 minutes; you can try Hive free for 14 days, no card needed.

What is AMENT Hive, and who is it for?

AMENT Hive is AI-assisted, human-approved production software that runs a 3D print farm from order to finished part on one screen. This guide covers what Hive does today, how it works, how you set it up and what it does not do yet. The AMENT Hive page has the short version.

Hive is moving fast, so we state the status of every capability: live, needs setup (a bot or an e-mail account, for example) and live but not yet tested on real printers, which we call being validated in the field. For a farm owner, “it works” and “it has been proven on the shop floor” are different claims, and we would rather keep them apart.

What breaks as a farm grows

With three printers, the job is running printers. With fifteen, the job becomes running an operation. The friction tends to come from the same places:

  • Scattered orders: Trendyol, your own shop and direct messages each live somewhere else, and working out what has to ship today is a spreadsheet job.
  • Split tools: Every printer brand has its own app. Switching between Bambu Handy, Creality Print and Mainsail stops you seeing the farm at a glance.
  • Knowledge in someone's head: Which file, which settings, which printer, which colour: often only one person knows. When they are off, production slows.
  • Missed deadlines and late failures: A print that finishes at night waits on the plate until morning, a part that lifted on the first layer is noticed hours later, a shipping deadline passes quietly.
  • Unknown costs: Filament stock lives in a spreadsheet or nowhere, and you learn a colour has run out when the spool is empty.

What these have in common is not a missing tool but missing links between tools. When orders, plans, files and printers sit in separate places, a person makes every connection by hand. We look at that wider picture in our guide to print farm management software.

What each kind of farm gets

Where Hive helps most, by farm size
FarmTypical situationWhat stands out in Hive
Small (3–10 printers)The owner does everything and sells on TrendyolOrders arrive on their own; one-click slicing, phone alerts, filament tracking
Medium (10–50 printers)Operators on shift, several printer brandsPlanning around shifts, the shop-floor screen, roles, a TV board, quality and maintenance
Large (50+)Several sites, high order volumeSwitching between farms, due-date estimates, connecting your own systems over MCP

Hive has five roles: owner, production manager, operator, technician and viewer. Every permission is checked on the server, not just hidden in the interface. Operators land straight on the shop-floor screen, and only owners and production managers can confirm a print start.

How Hive works: the architecture end to end

Hive has three parts: a web app in the cloud, a Farm Connector installed on a computer at the farm, and a cloud slicer. The design is deliberately simple. The less a system has to touch on a farm's network, the shorter the setup and the smaller the risk.

StoresTrendyolikasShopify+ orders entered by handAMENT HiveRuns in the cloudOrders · plan · filesCloud slicerOrcaSlicerHive AI assistantScreensWeb · phoneWorkshop TVTelegram · WhatsAppInternetFarm network · LANoutbound connection onlyno open portsFarm ConnectorMac · Windows · LinuxBambu LabCrealitySnapmakerKlipper
Hive's architecture: stores and screens connect to Hive in the cloud, while the Farm Connector connects outwards only and talks to printers on the local network.

The web app

Orders, the plan, files, the slicer and the assistant live in Hive in the cloud. You use it from a computer, from a phone (it installs to the home screen), on the workshop TV and, with some setup, from Telegram or WhatsApp. Hive runs in the cloud, and the interface is in English and Turkish.

The Farm Connector

The Connector is a small app installed on a computer that stays on at the farm (Mac, Windows or Linux). It finds printers on the local network, talks to them there, and connects outwards only to Hive. Because the connection is made from the inside out, you do not open ports on your router or expose your printers to the internet.

From version 0.12 the Connector installs signed updates on its own and rolls back if an update misbehaves. If the Connector drops or a printer becomes unreachable, Hive raises an alert.

The Connector does not need a powerful machine; what matters is that it stays on and sits on the same network as the printers. If that computer switches off, printers carry on with prints already running, but Hive can no longer see them and sends you a connection alert. So put the Connector on a machine that stays on, not an office PC that is shut down at night.

The cloud slicer

Slicing runs in the cloud with OrcaSlicer. One slicer for every brand means no separate program for Bambu and another for Creality. If the same file has already been sliced with the same settings, Hive reuses the result instead of slicing it again.

The journey of one order

End to end, the chain runs like this: an order arrives from the store, matches the product's approved print file, the planner places it on a plate and a printer, you approve the plan, the file is sliced for that printer, uploaded, started, monitored, and when it finishes the operator records the good parts. We take each link of that chain apart in order-to-print automation.

Orders, store integrations and the production plan

One order queue

Orders from Shopify, ikas and Trendyol land automatically in one queue. For ikas and Trendyol, setup is a matter of entering the API details from your store panel. On first connection, recent open orders come in (the last 13–14 days, depending on the store), and after that Hive checks every 10 minutes for anything it missed. Orders from other channels are entered by hand.

  • Shipping deadline: Trendyol's dispatch deadline shows on the order as “Ship by”; with less than 24 hours left it turns red, and the planner takes it into account.
  • Cancellation guard: An order cancelled or changed in the store is never silently removed from production; it is put on hold with a warning.
  • Unmatched products: Hive lists products without a print file, so a missing file shows up early rather than at planning time.
  • Sending status back to the store: Hive can mark orders “shipped” on ikas and “preparing/invoiced” on Trendyol. This is off by default, asks for approval per order, and is being validated in the field.

How the planner decides

The planner looks at three things, in order: urgent orders, the promised due date and the age of the order. Different materials or colours never share a plate. Each job goes to the suitable printer that will finish it soonest, where suitable means the right printer model, nozzle and loaded filament.

Plans are always prepared as a draft. You see the draft on a timeline, regenerate it if needed, and it only takes effect when you approve it. A print that has started is never moved; when a new order arrives, the plan only rearranges work that has not begun.

The draft-and-approve step is deliberate. The planner is fast, but it cannot know everything happening on the floor: a plate may be scratched, an operator may be leaving early. Reviewing and approving the draft takes a few minutes and keeps the plan in line with reality.

TodayPlanningDraft · rev 3DiscardApprove planPrinter08:0010:0012:0014:0016:0018:0020:00B1 · P1SHinge ×12Clip ×24Body ×2B2 · P1SFoot ×8Cover R ×4Holder ×6B3 · X1CHolder ×6Cover L ×4Case ×1K2 PlusBody ×1Lamp ×2U1Knob ×40Clip ×24NowPrintingPlannedDraftDoneOff shift
A simplified drawing of the planning screen: printing, planned and draft plates awaiting approval, the now line and long prints set for the night. Sample data.

Learned print times and “when will it be ready?”

A slicer's estimate does not always match a real printer. Hive learns how long each product actually takes on each printer and how often it fails. Ask “Will this order be ready by 2 pm tomorrow?” and you get two answers: the most likely finish time and the worst case.

Shifts and night electricity rates

Enter your shift hours and the planner puts long prints in the evening, so they run overnight and a short print that finishes when nobody is around does not leave a printer idle for hours. You can also switch on night rates: long prints move to cheaper electricity hours and the saving is shown. The reasoning behind units per plate and job order is in plate planning for print farms.

Files, cloud slicing and plate layout

On a farm, the most common mistake is the wrong file or the wrong settings. Hive answers that with a catalogue: each product (SKU) has an approved print file, and only approved profiles reach production.

Catalogue and versions

3MF, STL and G-code files are kept with their versions (v1, v2…). You can rename files, add notes, duplicate them and clean up storage. When you change a setting you upload a new version instead of overwriting the old one, so what was printed last month, and how, is never lost.

The cloud slicer

  • One slicer: OrcaSlicer for every brand, with saved setting sets, colour mapping, prime towers and thumbnails.
  • No repeat work: A file already sliced with the same settings is not sliced again.
  • AI setting suggestions (optional): Hive suggests settings from the file, the printer and past failures; nothing changes in the form until you press “Apply”.
  • Full OrcaSlicer in the browser (add-on): The real OrcaSlicer opens in the cloud, and whatever you save comes back to Hive as a new version.

The plate editor

You can split plates, duplicate them, copy and paste, name them and move the prime tower, in 2D or 3D. Hive works out the most efficient plate for each printer model and compares them by units per plate and units per hour. The “Fill to max” button in the editor builds that layout in one click.

Why slicing in the cloud makes sense for a farm, and where it has limits, is the subject of cloud slicing for print farms.

Printers, the Farm Connector and two-step sending

Supported printers

Printers Hive supports today
BrandModelsNote
Bambu LabA1, A1 mini, P1S, P2S, X1, H2DSending over FTPS + MQTT with AMS slot mapping; needs LAN Only and Developer Mode
CrealityK2, K2 Plus, Hi, K1CStock K1C is monitor-only: no file upload or start
SnapmakerU1Filament on each toolhead shown with colour and material
KlipperAny printer running MoonrakerSending and control through Moonraker

Adding printers

The Connector scans the network and finds printers by itself. Klipper, Creality and Snapmaker printers are added without a code. For Bambu printers you first switch on LAN Only and Developer Mode on the printer's screen (the access code changes when you do), then the printers found appear in one table: type the codes one after another and save them all at once. There is a Developer Mode guide per model and a “Try code” button; “Try code” is still being validated on real printers.

Live status and cameras

Each printer's progress, time remaining, temperatures and errors are live. Camera feeds are available on Creality, Bambu A1/P1 and Moonraker printers. Loaded filament (AMS, CFS, Snapmaker toolheads) shows with colour and material, and you can change the colour in Hive. Writing that colour back to the printer itself with “Also apply on the printer”, on Bambu and Snapmaker U1, is being validated in the field.

When a printer reports an error code, Hive explains in plain language what it means and what to do; when a Bambu printer pauses a print by itself because of a problem (filament run-out, for example), you get an alert with the same explanation. Both are ready in notifications and on the server, the web and iOS screens are being built, and both are still being validated on real printers.

Sending: two separate confirmations

Getting a sliced file onto a printer is two steps, and both need a person. First upload: the file is transferred to the printer, with AMS slots mapped on Bambu. Then start: only an owner or production manager can do this. Right before a start, the server checks four things again:

  • the plate is clear (someone has confirmed “plate cleared”);
  • the printer is idle;
  • the right filament is loaded;
  • the file was sliced for this printer.
How a job reaches a printerAI boundaryHive AIPreparesPicks a printerChecks filamentSlices the fileProposalConfirm 1UploadFile transferredAMS slotsmappedUploadServerChecksPlate clearPrinter idleRight filamentRight sliceLoggedConfirm 2StartOwner orproductionmanagerStart printBeing validated in the field
How a job reaches a printer: Hive prepares, a person confirms the upload, the server runs its checks, a person confirms the start.

Remote control

Pausing a running print from Hive, resuming a paused one or cancelling it works on Bambu and Klipper/Moonraker printers (not on a stock Creality K1C). On Bambu you can clear the error on the printer's screen once the problem is fixed, and start calibration remotely: bed levelling and vibration compensation on Bambu, homing and a bed mesh on Klipper. Calibration moves the toolhead and bed, so it only runs when the printer is idle, the plate has been confirmed empty and no job is on its way to that printer.

Only an owner or production manager can send these commands, by confirming in the app. The server re-checks the printer's live state each time; a command is delivered once, and if it does not reach the Connector within 2 minutes it is cancelled and will never run later. Every request, including refused ones, is logged. The server side is ready, the buttons are being built for web and iOS, and all remote commands are still being validated in the field. More in remote printer control.

Hive AI assistant: cards, approvals, MCP and budget

Hive AI is a production assistant that works with your farm's real data. It reads printers, orders, the plan, filament and the catalogue, and answers questions like “Where are we?”, “Is anything failing?” or “When will B6 finish?” in English or Turkish. Its answers come from your farm's current state, not from guesswork.

The most useful questions during the day are short and concrete: “What won't we make today?”, “Which filament is running low?”, “Which prints run overnight?”, “Can this order be ready by 2 pm tomorrow?”. The assistant answers from the planner, the filament forecast and live printer state, so you do not open those pages one by one.

Cards: a conversation that behaves like a screen

  • plate images and printer cards;
  • clickable quick replies;
  • shortcuts above the message box for things you ask often.

It prepares, you approve

Say “send this to an idle K2” and Hive picks the printer, checks the filament and slices the file if needed. Then an approval card appears: first “Upload to printer”, then “Start print”. Say “make the Creality Hi pastel blue” and you get an Apply/Cancel card; maintenance mode changes the same way. Say “put four left covers on one plate” and a draft opens in the plate editor.

MCP, Telegram and WhatsApp

Hive's MCP server lets AI apps such as Claude connect to your farm; we walk through it step by step in connect Claude to your print farm. The same assistant can answer on Telegram and WhatsApp too, which needs a bot to be set up. Whichever channel you ask from, approvals are always given in the Hive app.

Keeping AI costs in check

Each farm has a monthly AI budget. The same question is not charged twice, and models are chosen from the most economical class that does the job. Where AI genuinely helps on a print farm, and where it does not, is the subject of AI for 3D print farms.

Filament, quality, maintenance, team and notifications

OrdersTrendyol · ikas · ShopifyShip-by, cancel guardUnmatched productsStatus back to storePlanningDraft plan and approvalLearned print times“When will it finish?”Shifts and night ratesFiles and slicingVersioned catalogueCloud OrcaSlicerPlate editorAI setting suggestionsPrinters, sendingFarm Connector, camerasSending, two confirmsRemote controlError explanationsHive AIChat and cardsApproval cardsMCP, monthly budgetTelegram · WhatsAppFilament · quality · teamFilament forecastCamera failure alertsMaintenance, alertsE-mail invitationsLiveNeeds setupBeing validated in the field15 October 2026
Hive's features by area, each marked with its status: live, needs setup, or being validated in the field (as of 15 October 2026).

Filament stock and forecasts

Hive records grams per print and use per printer. Add your spool stock and price per kilo, and you see how much of each colour and material you use, your monthly need and a reorder list. Warnings are concrete: “white PETG lasts 9 more days, order by Tuesday”. How the forecast is worked out is in filament stock forecasting.

Camera failure detection and quality reports

Optional camera analysis sends a photo alert for spaghetti, parts lifting off the plate and layer shifts. It never stops a print on its own; you decide. The quality report breaks the failure rate down by printer, product, filament and time of day, with the most common causes. So “why does this part keep lifting on this printer?” becomes a question you answer with data. Details in print failure detection and quality.

Maintenance reminders

Maintenance is due by print hours, not by calendar: “B3 nozzle check, 300 hours”, for example. Put a printer into maintenance mode and the planner stops giving it work.

Team, notifications and mobile

  • Team: invitations and roles, password reset, open sessions, switching between farms. Invitation e-mails switch on once the e-mail service is set up.
  • Shop-floor screen: a phone-friendly screen for operators; “plate cleared”, “done (good parts)”, “failed (reason)” in one tap.
  • TV board: the live state of every printer on the workshop TV.
  • Notifications: an in-app feed, phone push (web push), e-mail, Telegram, Discord and Slack. Per-person preferences and quiet hours are planned.
  • Mobile: an app you can install on your phone (add to home screen) with a bottom tab bar. App Store and Google Play apps are the next stage: the iOS app is written but not yet submitted, and the Android app is in progress.

How to set up the shop-floor screen, the TV board and alerts so they work together is covered in print farm notifications and floor display.

Security and trust: how Hive protects your data and printers

Giving software access to your printers takes trust. Hive's approach to security rests on one idea: software prepares, a person approves, and every step is recorded.

  • Printers stay off the internet: The Connector talks to printers on the local network and connects outwards only to Hive. Nothing needs to reach into your farm's network.
  • Farm data kept apart: Each farm's data is fully separated from every other farm's, and automated tests check that separation in every release.
  • Audit log: Every change is logged; for remote commands, refused requests are logged too.
  • Encryption: Printer access codes and API keys are stored encrypted.
  • The AI boundary: The assistant cannot start a print, upload a file or command a printer. A person always approves.
  • Signed updates: Connector updates are signed. Even if the Hive server were compromised, it could not push malicious code to Connectors.
  • Permissions on the server: Role checks and pre-start checks run on the server, on every request.

These rules are a design choice more than a feature list. A fully automatic farm sounds appealing; yet if the last print is still on the plate or the wrong colour is loaded, a system that never asks makes the mistake bigger. In Hive, automation does the preparation and a person makes the call.

Getting started with Hive: setup and a recommended daily flow

First setup takes about 30–45 minutes. We can do these steps with you if you like, but the order is the same on every farm:

  1. 1

    Create your account

    Enter the farm name and time zone. Add shift hours under Settings → Farm; the planner places long prints around them.

  2. 2

    Install the Connector

    Put it on a computer that stays on at the farm: a Mac mini, an old laptop or a Linux machine such as a Raspberry Pi. Download it from the Connector page in Hive, open it and approve it in the browser.

  3. 3

    Add your printers

    The Connector scans the network. For Bambu printers, first switch on LAN Only and Developer Mode on the printer's screen and read the new access code; type the codes into the table one after another and press “Save all”. Klipper, Creality and Snapmaker printers need no code.

  4. 4

    Connect your stores

    Integrations → ikas, Trendyol or Shopify. Enter the API details from your store panel; recent open orders come in by themselves.

  5. 5

    Build the catalogue

    Upload the 3MF for each product and match it to its SKU. If useful, save the layout that fits the most units in the plate editor.

  6. 6

    Invite your team

    Settings → Team. Operators land straight on the shop-floor screen.

  7. 7

    Turn on notifications

    Settings → Notifications: phone push, e-mail, your team channel. The Telegram and WhatsApp assistant needs a bot to be set up.

  8. 8

    Connect the workshop TV

    Displays → new display. Open the link it gives you in the TV's browser.

A recommended daily flow

A recommended dayMorningProduction managerOvernight resultsApprove the planAsk the assistantDaytimeOperatorRecord good partsPlate clearedConfirm next startEveningBefore leavingStart long printsAsk on TelegramOvernight runWeeklyOnce a weekReorder filamentQuality reportMaintenance listHive prepares, you approve.
A recommended production day with Hive: approve the plan in the morning, run the shop-floor screen during the day, start long prints in the evening, review filament and quality weekly.
  1. 1

    Morning: owner or production manager

    On the overview, check prints that finished overnight, errors and what must ship today (the red “Ship by” ones). In Planning, generate the new plan, review it and approve it. Ask the assistant: “What won't we make today?”, “Which filament is running low?”

  2. 2

    Daytime: operator

    On the shop-floor screen (phone or tablet), record the good parts from each finished print and confirm “plate cleared”; for a failure, pick the reason. When the next start confirmation comes up, check the printer in person and start it.

  3. 3

    Evening: before leaving

    Start the long prints the planner suggests for the end of the shift. On the way home you can ask on Telegram: “Which prints are running overnight?”

  4. 4

    Weekly

    Check the filament forecast and pull the reorder list. In the quality report, find the product and printer with the most failures and update the maintenance list.

Good habits

  • Keep one approved print profile per product; upload changes as a new version.
  • Keep filament colours and materials accurate. AMS and CFS report them already; for external spools, update them in Hive by hand.
  • Do your first sends standing at the printer, and go remote once you trust the flow.
  • If the access code changes while Developer Mode is on, Hive warns you; enter the new code on the bulk-add screen.

What Hive does not do yet, the roadmap and pricing

When you introduce a fast-moving product, the most useful information is what does not work yet. We would rather keep this list honest than short.

Open limits

  • Bambu and Developer Mode: Sending prints to Bambu printers from third-party software needs Developer Mode, and in Developer Mode Bambu Handy and the Bambu cloud do not work. That is Bambu's rule, not something specific to Hive.
  • Creality K1C (stock): Monitoring only; file upload and start are not supported.
  • Infrastructure: The system currently runs as a single server instance. As it grows, we plan to move file storage and locks to shared infrastructure.
  • Out of scope by choice: invoicing (including Türkiye's e-Arşiv) and shipping labels. Keep using your store panel or accounting software for those.

Still being validated in the field

The following are live but have not yet been tested on real printers. The first runs will happen with the farm owner present:

  • sending to Bambu and starting on Moonraker (including the two-step confirmation and pre-start checks);
  • writing colour back to the printer (Bambu, Snapmaker U1) and “Try code” in Bambu bulk add;
  • remote pause, resume, stop, error clearing and calibration;
  • plain-language error explanations and pause-with-error alerts;
  • sending order status back to the store;
  • the Windows Connector.

The roadmap

What comes next is a plan, not a promise, and priorities may shift with feedback from farms. What we are working on or have lined up:

  • a first-run setup wizard;
  • order search and paging, and a “Pending work” list;
  • a signed Mac Connector and a Windows app;
  • App Store and Google Play apps (Connector pairing by QR code, reading access codes with the camera, actionable notifications);
  • cost and profit analysis;
  • subscriptions and payments, data-protection documents, backups and monitoring;
  • capacity sharing between farms (this needs its own design).

If you are weighing Hive against another farm tool, Hive vs Printago sets out how the two approaches differ.

How to try Hive and what it costs

You can try everything in the Pro plan free for 14 days; no card needed. If you do not pick a plan when the trial ends, your farm continues on the Free plan and no data is deleted. Paid plans are Starter ($19), Pro ($49) and Business ($129) per month, with two months free on yearly billing. Full OrcaSlicer in the browser is a separate add-on ($15 per month). Details are on the pricing page. If you like, we connect the Connector, your printers and your store together with you, and do the first sends side by side.

Frequently asked questions

What is AMENT Hive?

AMENT Hive is AI-assisted production software for 3D print farms. It gathers Trendyol, ikas and Shopify orders, plans production, slices files in the cloud and shows Bambu Lab, Creality, Snapmaker and Klipper printers on one screen. A person approves every physical step.

Which 3D printers does Hive work with?

Bambu Lab (A1, A1 mini, P1S, P2S, X1, H2D), Creality (K2, K2 Plus, Hi; stock K1C for monitoring only), Snapmaker U1 and any Klipper printer running Moonraker. Sending to Bambu printers needs LAN Only and Developer Mode. Sending to printers is live and being validated in the field on real printers.

Can Hive AI start a print by itself?

No. The assistant picks a printer, checks the filament and prepares an approval card; uploading the file and starting the print are two separate human confirmations. Only an owner or production manager can start a print, and remote commands such as pause, stop and calibration are never available to the assistant.

Do I have to expose my printers to the internet to use Hive?

No. The Farm Connector, installed on a computer at the farm, talks to printers on the local network and connects outwards only to Hive. You do not open router ports or allow access into your network, and Connector updates are signed.

How long does it take to set up Hive?

First setup takes about 30–45 minutes: account, Connector, printers, store connections, catalogue, team, notifications and the workshop TV. We can do the setup together with you if you like.

Is Hive available now, and how much does it cost?

Yes. You can try Hive free for 14 days, no card needed. Plans are Free, Starter ($19), Pro ($49) and Business ($129) per month, with two months free on yearly billing. Details are at ament.ai/en/hive/pricing.

Run your print farm with AMENT Hive

Try Hive free for 14 days; no card needed.