Show HN: Iceburg CRM – Open-Source Meta Driven CRM Using Vue3 / Laravel

This is a meta driven CRM which basically means you can define modules, fields, subpanels, etc and generate a crm from that data. It was partly inspired by SugarCRM and other CRMs I have worked on over the years.

I've been working on php based CRMs for 10 years and I thought it was time I created my version of a CRM. At first I want to built a typical business CRM but also a personal CRM. Wouldn't it be cool to be able to build niche crms like a stamp collecting CRM or a social CRM. So I build the CRM in a way where it can become any crm.

The big feature that separates this CRM from other CRMs is how I handle relationships. Instead of having fields withing tables that link modules together with pivot tables and between modules I went with a different strategy where I have a relationship record that holds the relationship for each record. This allows me to create relationships with unlimited number of unrelated modules. And these can be reused in different subpanels.

This is useful for subpanels and removing unnecessary fields from primary module tables. For example: account / contacts might be a subpanel and another subpanel might be contract signing which would hold the: account / contacts / user / city / state / country information. Normally the contracts module would need to contain those specific (contract signing) fields Those fields do not need to exist at that level and can live in the relationship structure.

We still have traditional relationships like related fields where a field in one module would represent a value from another module.

I spent the last 5 months working on this project in my off hours. I've tried to do something each day and that helped keep the project moving along.

Many features planned like automation and admin tools for changing the structure of the crm from the dashboard I had to cut out of this version.

Give it a try.

Some of the other unique items.

When exporting related fields (which are represented as an id that links to another module's value) the value is subbed in. When importing the opposite happens where the value is converted back to an id if possible.

Convertable modules where you define target modules where same name fields convert. Handy for converting leads to contacts, etc