ERP and MRP platform
Your production, stock and invoicing in one system
Alibera plans production orders, keeps stock honest and issues the invoice at the end of the same record. It also reads the machines on your floor. Run it in the cloud or on a server you own.
Built and supported by a small team. We look at how your company already works, then configure the modules around it.
01The product
What your team opens every morning
A production board, stock with what is reserved and what is free, and an invoice with its fiscalization status. Three views of the same records, not three systems.
Production orders move across the board. The quantities and the progress come from the records the plan is built on, so the board is not a separate spreadsheet someone keeps up to date.
What is on hand, what is already committed to open orders, and what is actually free to use. A low row is flagged where it happens, not in a report someone runs on Friday.
The invoice is issued from the same order the board finished. Fiscalization is handled inside the accounting module.
The three screens above are illustrations of the Alibera interface with sample data. No customer data and no figures are shown.
02The platform
A core, and the modules you actually use
Alibera is a platform of modules rather than one fixed product. Everything writes into the same core, so a module you add in year two reads the data that is already there.
Core
The core
The base ERP and the shared database every module writes into. Production planning sits here: bills of material, make to order and make to stock, planned against the stock you actually hold.
- Available
Accounting
Your books in the same system as production and stock, with FURS fiscalization.
- Available
Point of sale
Our own till, running on the same product and stock records as everything else.
- In development
Logistics
Goods in, goods out and the stock records behind them. Being built now for a live customer project.
- In development
Field Ops
Work your people do away from the shop floor. On the roadmap, not finished.
- In development
Bookings
Reservations. The scope is not fixed yet, so we would rather describe it once it exists.
The core, accounting and point of sale are usable today. The other three are marked because they are still being built. You get that answer here rather than on the third call.
See every module in detail03What changes
What is different once it is running
Four things a production company notices first. None of these is a projection. Each one is what the system does.
- Planning
One plan instead of four spreadsheets
Production orders, bills of material and stock live in one database, so the plan is not rebuilt by hand every time an order moves.
- Stock
Reserved and free, not just on hand
Stock shows what is committed to open orders and what is genuinely available, so a date you promise a customer is made against a real number.
- Invoicing
The invoice and the goods behind it
Accounting sits in the same system as production and stock, so a document and the delivery it belongs to are never in two places. FURS fiscalization is part of the accounting module.
- Machines
The ERP can read the machines it plans for
Alibera connects to the equipment on your floor. It reads data from it, and it can send control commands back to it, so the plan and the machine are working from one set of numbers.
- Reads and controls
- CNC machines
- Omron PLCs
- Universal Robots
- Other IoT devices
Machine integration is built against a REST API that requires security keys and signed tokens. Every change is written to the audit trail with the user, the time and what was done.
How machine integration gets built04Rollout
How an implementation actually runs
Nothing gets configured until we agree on what your process is. The early part is mostly us listening.
Discovery
Meetings and a questionnaire to map your process, the systems you run today and the modules you would need.
Proposal
An implementation plan, a timeline and a quote, written against what we found rather than against a package.
Configuration and data migration
Modules are configured and your old data is exported and brought across. An NDA is signed before any export changes hands.
Testing and training
You validate the system in a staging environment. Your people are trained module by module, online or on site, from the basics upward.
Go live and the weeks after
We switch over and stay close, with active monitoring, quick fixes and more training wherever it is needed.
A small company can be finished in about a month. A larger one with a complex migration can run to six months or more. The rollout can be phased, core functions first and the rest after, so less of your week is disrupted at once. You get the honest range for your case, not the best case.
Read the full implementation process05Trust
Where the data sits, and who can reach it
The short version, with the gaps left in.
- Hosting
On-premise, the data is on your own server and you control it. In the cloud, we host it with providers in Slovenia or the EU. An on-premise installation keeps running whatever happens to us, and data can be exported from either one.
- Access
Permissions by role, department or location, configured per customer. Two factor login is on by default in the cloud and available on-premise. Every login, change and deletion is logged with the user, the time and what was done.
- Backups
Encrypted, stored away from the live system, and taken daily or weekly depending on how critical your system is. In the cloud our team runs the restore. On-premise you can run it yourself.
- GDPR
We follow GDPR. Your data is not moved out of the country without your consent, and processing is limited to what the contract covers. You can test a change in a separate environment before it reaches production.
This page carries no certification badge, no named data centre and no uptime figure, because those are claims we have not had verified. Ask us and you get the real answer.
Read the full security pageWill it fit the way we work?
Your processes are analysed before anything is configured, and the modules are set up to match them. Where a step is genuinely non-standard, it can be built as a custom module or an adaptation. Non-standard work is the case we are built for.
Can we keep the data on our own server?
Yes. On-premise means the data sits on your hardware and you control it, which is also what we recommend when machines have to be integrated on site. Cloud installations are hosted with providers in Slovenia or the EU. Data can be exported from either one.
What does it cost?
Pricing is a core plus the modules you use, priced per company and per user rather than per document or per transaction. Cloud is a subscription, billed monthly or yearly. On-premise is a one time licence plus setup and maintenance. We publish no price list, because the quote follows the modules you need and the number of people using them.
Is a small supplier a risk for something this important?
The people who analyse your process are the people who stay on the project. On the risk itself: an on-premise installation keeps running regardless of what happens to us, cloud customers keep the service for as long as they pay for it, and your data can always be exported to another system.
What is the relationship with Odoo?
Alibera is built on the Odoo 18 stack. We are not an official Odoo partner and we do not present ourselves as one. What you buy from us is a configured, supported product with local modules and local support, rather than a vanilla Odoo installation you configure and maintain yourself.
Nineteen production categories, described one by one
We publish no customer logos, because client names sit under NDA. Each category has its own page describing the processes we configure for it.
- Metalworking
- Plastics and rubber
- Electronics
- Food and beverage
- Industrial equipment
- Packaging
- Automotive
- Wood
- Browse the industry categories
Tell us what you make
A demo is a conversation about your process, your machines and the systems you already run. You get an honest answer on whether Alibera fits, including when it does not.
There is no package to pick from. The quote follows the modules you actually need and the number of people using them.