BIM and ERP for engineering offices — in the browser.

Open a 3D building model on any device with no plugin and no CAD licence per seat. Import IFC in the browser, and push element quantities straight into your ERP as project lines. It runs on your own server, so the models and the accounts stay yours.

Open the demo See a live model — no sign-in Install it on your own server

The second link is a share link: read-only, one model, exactly what you would send a client.

Built on open source, kept auditable · ChertERP — iDempiere 13, GPLv2 · Arabic and English

What you get

Six things it does today

Everything listed here is running and evidenced — not a roadmap.

Browser-native 3D

The model opens in the browser itself — desktop, tablet or phone. No viewer to install, no per-seat CAD licence, nothing to configure on the site engineer's laptop.

Many projects, many clients

One deployment hosts every project, each with its own model set. Access is scoped per tenant: a session for one client cannot read another's models.

IFC import, in the browser

Drop an IFC file into a project and it is compiled where you stand — no upload to a third-party service, no conversion desk. The model is then open to everyone the project is shared with.

Quantities into the ERP

Element counts per IFC class become project lines in the ERP, with derived volumes clearly labelled as estimates. Re-import a revised model and the lines update in place instead of duplicating.

A real ERP, not a stub

ChertERP is a full iDempiere 13 distribution: tenants, roles, organisations, projects and an accounting schema in SAR — with an Arabic interface of over six thousand translated elements.

Share one model, revoke it later

Hand a client or a contractor a read-only link to exactly one model — no account, no access to anything else — and revoke it from the project page when the job is done.

How it works

Three parts that stay separate on purpose

The 3D runtime, the ERP and the platform layer are deliberately not one merged application. Each can be replaced, audited or upgraded without dragging the other two with it.

1 · BIM runtime

Draws the building

  • Renders the model in the browser
  • Compiles IFC into a compact model database
  • Kept byte-identical to its open-source upstream
2 · ChertERP

Runs the business

  • Tenants, users, roles and organisations
  • Projects, project lines and accounting in SAR
  • It is the single source of identity — the viewer keeps no passwords
3 · Platform layer

Joins the two

  • Hosts every project's models, scoped per tenant
  • Signs users in against the ERP
  • Carries quantities from a model into a project

Why it is built this way

What an engineering office actually gets out of it

Your data stays on your server

One Debian server you control holds the models, the projects and the accounts. There is no third-party model store, and no tenant of ours between you and your client's drawings.

Arabic is not an afterthought

The ERP ships with a full Arabic interface, and this site and the guides are bilingual. Accounting is set up in Saudi Riyal from the first day, not converted later.

No licence per engineer

Because the model opens in a browser, the cost of adding the tenth person to a project is zero. Site staff read the same model as the design office, on the phone in their pocket.

Open underneath, and auditable

The 3D/BIM engine is open source under the MIT licence and the ERP is iDempiere under GPLv2 — kept auditable, with their copyrights and licences intact. Nothing here is a black box you cannot leave.

Self-host

One script, one Debian server

Start from a plain Debian or Ubuntu droplet. The installer sets up the viewer host, the web server and TLS, and can install the ERP alongside it.

cd chertengineering
sudo ./install.sh --domain app.example.com --email you@example.com
The source and the installer are distributed privately, not from a public repository. Ask us for access and you get the repository, the three guides, and the pinned runtime — the same build that runs the demo.

  1. Point a name at the server

    An A record for the hostname you will use. The installer requests the certificate itself once the name resolves.

  2. Run the installer

    It installs the runtime, the service and the web server, and refuses to trample an existing site rather than taking one down.

  3. Create your first project and import a model

    From the browser: create a project, drop an IFC into it, open it, and share it with whoever needs it.

The installer is written for a server you own. It is not a hosted service, and we hold no copy of your models.

Documentation

Guides

Three guides, each written for a different reader, in English and Arabic. They ship inside the repository alongside the installer.

Installation guide

What the server needs, what the installer does, how to put it behind a name with TLS, and how to undo it.

English and Arabic · ships with the software

Administrator guide

Tenants and users, backups and restores, certificates, upgrades, and what to check when something looks wrong.

English and Arabic · ships with the software

User guide

Signing in, creating a project, importing an IFC, moving around the model, sharing a link, and sending quantities to the ERP.

English and Arabic · ships with the software