← Back to overview

Senga

ERP & database integration for Belgian enterprises

Question every source you already use.

Senga connects fragmented systems (ERPs, databases, spreadsheets, BIM models) into a single queryable workspace. No data duplication, no migration headaches. Just your data, finally talking to itself.

— STATUSLive— CATEGORYData Integration— AUDIENCEEnterprise + Ops
— How Senga is built

Four layers between your systems and your team.

Senga does not copy your data into one more silo. It reads each source where it lives, gives every record one shared shape, and puts the result to work in the tools your team uses every day.

PostgreSQLSAPOdooExcelIFC / BIMREST APIMySQL{ }CONNECTORSKUNNRcust_noclient_idNETWRamount_untaxedTotal HTclienttext · keyamount€SCHEMA REGISTRYSCAN sapSCAN odooJOIN clientSCAN ifcFILTER lateΣ amountQUERY ENGINESTOCKBIM VIEWERCRMDASHBOARDSQUOTESE-INVOICINGWORKSPACE
Point at a layer or a module card.
  1. L / 04

    Workspace

    Quotes, PEPPOL invoices, stock, CRM, HR and assets. Every module works on the same objects, so a project, its client and its open invoices sit one click apart.

  2. L / 03

    Query engine

    Ask one question across an ERP, a database and a spreadsheet at once. Answers are cached, so the second time is instant.

  3. L / 02

    Schema registry

    Columns from different systems map to one set of fields and types. A client ID in Odoo and a customer column in Excel become the same thing.

  4. L / 01

    Connectors

    PostgreSQL, MySQL, MongoDB, Oracle, SQL Server, Odoo, SAP, Excel, Google Sheets, IFC models and REST APIs. Each one tested in a click and read in place.

— Building blocks

Six ideas carry everything.

Learn these six and you know how Senga thinks. Every screen, question and module is made of them.

> 30 daysodoo · ifcquotes · crmCLIENTQUOTEINVOICESTOCKBIM MODELASSETPROJECTPROJECT · PRJ-2026-014StatusOn siteBudget€ 1.24MOpen quotes3Unpaid invoices2BIM elements18,402Sources4OBJECTSPROPERTIESLINKSSOURCESQUERIESMODULES
Point at an idea, or at an object on the plane to open it.
  1. B / 01

    Objects

    A real thing your business tracks: a project, a client, a pump, an invoice. One object, even when its data sits in five systems.

  2. B / 02

    Properties

    The facts about an object. Each one traces back to the source column it came from.

  3. B / 03

    Links

    How objects relate. A project has a client, quotes, invoices and the BIM elements it is built from.

  4. B / 04

    Sources

    Where the facts live. Senga reads them in place, without moving or copying them.

  5. B / 05

    Queries

    Questions that cross sources, like every unpaid invoice on a project running late.

  6. B / 06

    Modules

    The working tools on top: quotes, invoicing, stock, CRM. They all share the same objects.

— In and out

Every source in. One answer out.

Data comes in from the systems you already run. Senga links it into objects, and answers go out as quotes, invoices, dashboards and reports.

SOURCESPostgreSQLOdooExcelSAPIFC / BIMSQL ServerREST APIGoogle SheetsANSWERSQuotePEPPOL invoiceDashboardStock alertReportProject viewAsset sheetClient filelinklinklinklinklinklinkProjectstatus · on site→ 3 quotesodoo · ifcClientVAT · BE0412…→ 6 projectssap · excelQuotetotal · € 48.2k→ clientodooInvoicedue · 30 days→ projectodoo · rest apiSENGAAssetservice · 03/27→ BIM elementpostgresSupplierlead time · 5 d→ 14 itemssap · sheetsStock itemon hand · 42→ suppliersql serverBIM elementIfcPump · L2→ assetifc
Point at a source, an object or an answer to follow its path.
  1. 01

    Read in place

    No migration project. Your ERP stays your ERP, and your spreadsheets keep working.

  2. 02

    Linked once

    Each record is matched to its object one time. After that, every module reuses the match.

  3. 03

    Answers anywhere

    The same objects feed screens, documents and reports, so the numbers agree everywhere.

— Capabilities

F / 01

Universal Connectors

PostgreSQL, MySQL, MongoDB, Oracle, SQL Server, Odoo, SAP, Excel, Google Sheets, BIM/IFC files, REST APIs. More than 11 source types, with one-click testing.

F / 02

Virtual Schema Registry

Automatic column mapping and type normalization across sources. Your data speaks one language without being moved.

F / 03

Cross-Source Querying

Query across databases, spreadsheets, and ERPs in real-time. Smart caching keeps it fast.

F / 04

Business Operations

Built-in quotation engine, inventory management, and PEPPOL e-invoicing. Not just a data tool. A business platform.

F / 05

Project & Resource Management

CRM, HR, asset tracking, and file management modules. All connected to the same unified data layer.

F / 06

Secure by Design

SSL/TLS encryption, no data duplication, self-hosted deployment. Your data never leaves your infrastructure.

— Built for
  • A / 01

    Enterprise teams managing fragmented data across multiple ERPs and databases

  • A / 02

    Construction and infrastructure companies working with BIM models and operational data

  • A / 03

    Operations managers who need real-time visibility across disconnected systems

— Where it comes from

Senga was born from one of the hardest data challenges in the construction industry: massive, disconnected information silos. We recognized that even a complex 3D BIM model is just a database of objects and metadata. By focusing on interconnecting siloed data rather than just viewing models, we built an approach to data unification that now works across any industry.

— Frequently asked

Questions worth asking.

What is BIM integration and why does it matter?

BIM (Building Information Modeling) files like IFC contain a database of every object in a building: equipment, rooms, materials. Senga reads that database alongside your ERP and CMMS so a maintenance request can pull live data from the model, the inventory system, and the procurement ledger in one query.

Can I keep my data on-premise?

Yes. Senga is self-hosted by default. It runs on your infrastructure, behind your firewall. Cloud is an option, never a requirement. Your data never leaves your jurisdiction.

Which ERPs and databases does Senga support?

Out of the box: PostgreSQL, MySQL, MongoDB, Oracle, SQL Server, Odoo, SAP, Excel, Google Sheets, IFC/BIM files, and any REST API. Custom connectors take days to build, not months.

Does Senga handle PEPPOL e-invoicing?

Yes. Belgian e-invoicing via PEPPOL is built in, including UBL document generation and access-point integration. Your invoices are compliant the day you go live.

How is Senga different from a typical iPaaS like Zapier or Make?

Zapier moves data between apps with triggers and actions. Senga unifies data so you can query across systems without moving it. Different problem: orchestration vs. integration.