Skip to content

Install the Ecosystem

Jump to bottom
Andrea Bruno edited this page Sep 14, 2026 · 1 revision

Install the AI ERP ecosystem

This guide takes you from an empty machine to a working setup where an AI agent runs your company inside the ERP. By the end you will have three programs connected:

  • AI ERP — the ERP that holds your data and runs the real business operations.
  • AgentBridge — the chat front-end where you talk to the agent.
  • ErpTool — the plugin that lets the agent drive the ERP.

There are two ways to install:

  • The wizard (recommended): one script asks a few questions and sets everything up for you.
  • Manual: the step-by-step reference below.

The three parts

Part Repo Job
AI ERP Graphene-Lab/AI-ERP Stores the data, runs the real operations, enforces the rules and permissions.
AgentBridge Graphene-Lab/AgentBridge The chat front-end and the agent runtime (AIOrchestrator). You talk here.
ErpTool Graphene-Lab/ErpTool Turns the agent's decisions into secure calls to the ERP. Runs inside AgentBridge as a plugin.

How a request flows:

You (plain language)
   ↓
AgentBridge  →  AIOrchestrator (the agent)
   ↓  picks a tool and a method
ErpTool  →  HTTPS + JWT  →  AgentApi  →  AI ERP managers  →  your data

The agent never touches the database directly. It acts as a normal ERP user, so the same permissions and checks that protect your data from people also apply to the agent.

Prerequisites

  • PostgreSQL 14 or newer, running and reachable from the ERP.
  • A machine that can run .NET 10 apps (Windows or Linux). The released AI ERP archive is self-contained, so you do not need to install .NET yourself.
  • An LLM provider and an API key for AgentBridge (OpenAI, Gemini, DeepSeek, a local model, and so on).

Option A — The wizard (recommended)

The wizard installs AI ERP, PostgreSQL (if you want it installed), AgentBridge and the ErpTool plugin, asks a few questions about your company in your own language, and leaves you with a working system.

Run it from the AI ERP repository:

# Linux / macOS
bash tools/setup-wizard.sh
# Windows (PowerShell)
.\tools\setup-wizard.ps1

The wizard asks, in the language of your machine (English, Italian, French, Spanish, German, Russian):

  1. The company name, legal name, VAT number, address, city, country.
  2. The default currency (for example EUR).
  3. The PostgreSQL connection (host, port, user, password, database).
  4. The ERP account the agent will use (email and password).
  5. The AgentBridge download location.

It then:

  • writes your answers into bootstrap.json (the company setup file);
  • creates the database and starts the ERP, which builds the schema and the seed data;
  • downloads and installs AgentBridge;
  • installs the ErpTool plugin into AgentBridge's Tools/ErpTool/ folder;
  • writes the ERP connection so the tool can reach the ERP;
  • checks that everything is reachable and prints how to start.

When it finishes, open AgentBridge and start talking to the agent.

Option B — Manual install

Step 1 — Install and start AI ERP

  1. Create a PostgreSQL database the ERP can use, for example:

    CREATE DATABASE erp;
CREATE USER dev WITH PASSWORD 'dev';
GRANT ALL PRIVILEGES ON DATABASE erp TO dev;

  2. Set the connection string in AI.Erp.Site/config.json under Settings.ConnectionString:

    Server=localhost;Port=5432;User Id=dev;Password=dev;Database=erp;Pooling=true;

  3. Describe your company in AI.Erp.Site/bootstrap.json. This single file is the whole first-run setup. See the next section for its shape.

  4. Start the ERP. On the first start it creates its own tables, a default admin account, and everything in bootstrap.json. You do not run any setup command.

    dotnet AI.Erp.Site.dll --urls http://127.0.0.1:5080

  5. Check the setup with the status endpoint:

    TOKEN=$(curl -s -X POST http://127.0.0.1:5080/api/v3/en_US/auth/jwt/token \
  -H 'Content-Type: application/json' \
  -d '{"email":"erp@webvella.com","password":"erp"}' \
  | sed -n 's/.*"object":"\([^"]*\)".*/\1/p')

curl -s http://127.0.0.1:5080/api/v3.0/p/agent/setup-status -H "Authorization: Bearer $TOKEN"

    A good result looks like:

    { "success": true, "data": { "installed": true, "pending": false,
  "entity_count": 30, "seed_counts": { "company": 1, "customer": 6, "product": 12 } } }

The default admin (erp@webvella.com / erp) is for first-run only. Change it before any real use. See the Security note at the bottom.

Step 2 — Install AgentBridge

Download the latest release for your platform from Graphene-Lab/AgentBridge/releases, or use the one-line installer:

# Linux / macOS
curl -fsSL https://graphenelab.it/AgentBridge/install.sh | bash
# Windows (PowerShell)
irm https://graphenelab.it/AgentBridge/install.ps1 | iex

Start AgentBridge and set your LLM provider and API key (the guided setup in the TUI, or the provider config). See the AgentBridge README.

Step 3 — Install the ErpTool plugin

  1. Download the ErpTool release zip from Graphene-Lab/ErpTool/releases.

  2. Copy its contents into the Tools/ErpTool/ folder next to the AgentBridge program:

    <AgentBridge install>/Tools/ErpTool/ErpTool.dll  (+ its files)

    AgentBridge finds the plugin at startup, or adds it while it is running (hot-add, about 30 seconds).

  3. Tell the tool how to reach the ERP. Either set three environment variables before you start AgentBridge:

    Variable Example
    ERP_BASE_URL http://127.0.0.1:5080
    ERP_USER erp@webvella.com
    ERP_PASSWORD erp

    or write the file PersistentData/erp.json in the AgentBridge folder:

    { "baseUrl": "http://127.0.0.1:5080", "user": "erp@webvella.com", "password": "erp" }

  4. Turn the tool on. In the AgentBridge TUI, open Settings → Tools (the /tools command), find ErpTool in the list, and tick it. Save. The agent now sees the ERP methods.

Step 4 — Try it

In AgentBridge, ask the agent:

"List the ERP entities."

The agent calls get_schema and shows the tables. If it answers, the whole chain works.

The company setup file (bootstrap.json)

bootstrap.json is the single file that describes your company and the data model it needs. The ERP reads it on first start and creates everything. It has two parts: entities (the tables and fields) and seed (the starting records).

The company itself is one seeded record:

{
  "version": 4,
  "entities": [
    { "name": "company", "label": "Company", "labelPlural": "Companies",
      "fields": [
        { "name": "name", "type": "text", "label": "Name", "required": true, "unique": true },
        { "name": "legal_name", "type": "text", "label": "Legal name" },
        { "name": "vat_number", "type": "text", "label": "VAT number" },
        { "name": "address", "type": "multiline", "label": "Address" },
        { "name": "city", "type": "text", "label": "City" },
        { "name": "country", "type": "text", "label": "Country" },
        { "name": "email", "type": "email", "label": "Email" },
        { "name": "phone", "type": "phone", "label": "Phone" },
        { "name": "currency", "type": "text", "label": "Currency" },
        { "name": "default_warehouse_id", "type": "guid", "label": "Default warehouse" }
      ] }
  ],
  "seed": {
    "company": [
      { "name": "Northwind Traders", "legal_name": "Northwind Traders S.r.l.",
        "vat_number": "IT01234560123", "address": "Via Roma 10", "city": "Milan",
        "country": "Italy", "email": "info@northwind.example", "phone": "+39 02 1234567",
        "currency": "EUR", "default_warehouse_id": "@warehouse:WH1" }
    ]
  }
}

A link to another record is written as @entity:uniqueValue — for example "@warehouse:WH1" or "@payment_term:TP30". The setup resolves it to the real id when it applies the file.

The file also seeds the master data a company needs to start: VAT codes, payment terms, warehouses, customers, suppliers, products, price lists and more.

Safe to restart. The setup is gated by the SHA-256 hash of the file. If the file has not changed, the run is skipped. If you edit it, the change is applied on the next start. It only adds; it never deletes or renames. To start clean, drop and recreate the database.

Apply a change without a restart: edit bootstrap.json, then call POST /api/v3.0/p/agent/reprovision (the ErpTool reprovision method).

Example prompts

Once the tool is on, talk to the agent in plain language. A few examples:

  • "Add a customer named Rossi & Figli, email rossi@example.com, category wholesale."
  • "Create a quote for 10 of product SKU-1001 and 5 of SKU-1002."
  • "Turn quote Q-2026-0001 into an order."
  • "Deliver order SO-1042 and then invoice it."
  • "Record a payment of 1,200 against invoice INV-2026-0007."
  • "Raise a purchase request for 50 units of SKU-2002 from supplier Alfa."
  • "Receive the goods for purchase order PO-330 and register the supplier bill."
  • "Show the receivables aging."
  • "Which products are below their minimum stock?"

The agent reads the schema, picks the right method, and runs the real operation inside the ERP.

Daily scheduling examples

AgentBridge can run work on a schedule. Combined with the ERP, routine jobs run by themselves:

  • "Every morning at 8, invoice everything that was delivered yesterday and tell me the total."
  • "Every day, check stock and warn me about any product below its minimum."
  • "Every Monday, send me the receivables aging and list the overdue invoices."
  • "Every month, run a cycle count for warehouse WH1."

You set the cadence in plain language; the agent schedules the job, runs it on time, and records the outcome.

Security

  • The agent acts as the account in ERP_USER. Give that account only the permissions it needs.
  • Change the default admin password and the JWT key before a real deployment.
  • Keep the ERP credentials out of public repositories. Use environment variables or the PersistentData/erp.json file, which is not part of the program archive.

Troubleshooting

Symptom What to check
Tool says "no ERP connection is configured" Set ERP_BASE_URL, ERP_USER, ERP_PASSWORD, or PersistentData/erp.json.
setup-status shows installed: false The ERP has not finished first-run setup. Check the ERP log and that bootstrap.json is next to config.json.
Agent does not see ErpTool methods The plugin is not in Tools/ErpTool/, or it is not ticked in /tools.
ERP will not start PostgreSQL is not reachable, or the connection string in config.json is wrong.
pending: true in setup-status You edited bootstrap.json; call reprovision or restart the ERP to apply it.

Clone this wiki locally