Skip to main content
Sales and customersQuotes and costingA price per recipe, the same day.Orders and customer contactFrom quote to shipment, customer informed.Customer portalOrders, stock and certificates, for your customer.
ProductionPlanningOne current plan for the office and the floor.Production and operatorsWork instructions, scans and shift handover on the tablet.Quality and batch recordChecks, deviations and release without paper.
Warehouse and insightWarehouse and stockPer lot and location, picking by shelf life.PerformanceDowntime, OEE and what an order really cost.
How it worksFrom quote to shipment

Follow one order through your factory and warehouse, in eight steps.

See the steps →
Contract manufacturing and private labelYour customers are brands with high expectations.Co-packing and fillingFood and supplementsLot numbers, shelf life and labels per order.FoodSupplementsBakery and confectioneryBeveragesAnimal feed and pet foodChemicals and cosmeticsMixing and filling to order, documents per batch.Cosmetics and personal careCleaning productsPaints, coatings and adhesivesFlavours and fragrancesMake-to-order manufacturingMetal, plastics and assembly.Printing, packaging and labelsPlastics processingMetalworkingMachine and equipment buildingFurniture and interior fittings
Industry not listed?Do you produce to order?

Then Frontlink fits. Tell us which process takes you the most time.

Bring us one process →
IntegrationsYour ERP, email, Excel and databases, connected.Shop floor and machinesMachines, tablets and scanners, also when the internet drops out.AI and agentsAgents on your live production data. You approve.SecurityWhere your data lives and who can access it.GMP and validationHow you validate Frontlink for GMP manufacturing.
For your IT teamAPI and developer docs

How Frontlink connects, with an API for your own tools.

To the docs →

Answers for your IT, straight from the terminal.

Frontlink from the command line. Your IT team queries production data and manages Frontlink without clicking through screens, and AI agents that work in a terminal use it the same way.

Book a callDocumentation

What it is for.

The Frontlink CLI brings Frontlink to the terminal. You ask questions about runs, stops, batches and shipments, and manage parts of Frontlink such as the screen apps on your lines.

It is meant for IT teams who would rather type than click, and for AI agents that do their work in a terminal, such as coding agents. They use Frontlink through the same route as a person, under the same rules.

For
IT teams and AI agents that work in a terminal
What
Queries on production data and commands to manage Frontlink
Access
The permissions of the user behind it
Record
Every action recorded, human or AI

What you can do with it.

  • Output per line
    frontlink=> SELECT line, sum(bags)
frontlink-> FROM runs WHERE week=42;
 line 2 | 58200
 line 3 | 41700
  • Stops by reason
    frontlink=> SELECT reason, sum(min)
frontlink-> FROM stops GROUP BY 1;
 sealer fault | 34
 changeover   | 22
  • Batch status
    frontlink=> SELECT batch, status
frontlink-> FROM batches LIMIT 2;
 88213-A | released
 88214-B | in review
  • Screen apps on the floor
    $ frontlink screen-apps list
  filling    v5 · 3 lines
  weighing   v3 · weigh room

How you connect.

  1. Agree on access with us

    We look at who in your IT team works with the CLI and which agents may use it.

  2. Work as a user

    The CLI works with the permissions of the user behind it. An agent gets no more access than the person who runs it.

  3. Give your agents the same route

    AI agents that work in a terminal use the CLI the way a person does. Changes they prepare wait for approval.

  4. Everything in one history

    Every command and every change is recorded next to the work done in the screens, so you can always see who did what.

The same rules for every AI.

MCP, API and CLI are three ways in to the same Frontlink. Whichever one you use, these rules apply.

  • The same tools as Frontlink AI

    MCP, API and CLI open the same tools Frontlink AI uses. There is no separate back door with logic of its own.

  • Never more permissions than the user behind it

    Every request runs with the permissions of the person behind it. What they may not do in the screens, their AI or script cannot do either.

  • Changes wait for approval

    A change an AI prepares is a proposal. It only happens after someone with the right role approves it.

  • Every action recorded, human or AI

    Who asked, what changed and when, in the same history as the work done in the screens.

Other ways into Frontlink.

  1. MCPConnect Claude or ChatGPT. Ask about orders, planning and stock, and have changes prepared for your approval.
  2. APIA documented API your ERP, webshop or own scripts use to read and write, starting with the warehouse.

Frequently asked questions.

Who is the CLI for?

For IT teams who want to query or manage Frontlink from the terminal, and for AI agents that work in a terminal, such as coding agents.

Why would an AI agent use the CLI?

Coding agents already work in a terminal. The CLI gives them Frontlink in the place they work, with the same tools and the same rules as Frontlink AI.

Can the CLI change data?

Only within the permissions of the user behind it. Changes an AI prepares wait for approval, and every action is recorded.

Do we need the CLI to use Frontlink?

No. Most people work in the Frontlink screens. The CLI is an extra route for IT and agents.

Which process takes you the most time?

Book a 30-minute call. We show what Frontlink does with your own examples.

Book a call