Product How it works Channel, sheet, the record's run Architecture Espo on one side, the API on the other The model It proposes the mapping. It does not save. The run Cadence, and this morning's number Rules Owner, key, reject Sheets The ones Espo already has The field Who wins if the cell is empty The record How it enters and how it leaves What can go wrong Preview, read mode, the switch
Channels Channels File, table, call, outbound Recipes A mapping to review The trial The repository, an empty Espo
Nesso Why Nesso Not SQL, not a second CRM Who it is for Who has to trust the run Decisions The ones the code keeps The project The public repository
FAQ The trial
Italiano English

The trial

No sign-up. Clone it and start.

The repository is public. Docker Compose starts an empty Espo and the engine. Production dumps are not mounted.

Espo on one side

An empty Espo is the trial. A production dump is not.
How you start

The repository

The code is at github.com/nessocrm/nessocrm. There is no installer and there is no waitlist. Whoever wants to try clones the repository and reads the manual in the docs folder.

This page does not ask for an email address. There is no form. The contact is the repository.

What comes up

Docker Compose starts the database, an empty Espo, and the engine. The trial Espo stays empty: production dumps are not imported and attachments are not copied.

Writes toward Espo go through the HTTP API. No query on Espo tables. The Advanced Pack, if someone has it locally, is not in the repository and is not published.

What stays off

Write-back, retry queue, portal filter, seal: off. The NESSO_SECRET_KEY variable is not set, so a password saved in the trial stays cleartext on the volume. It is written in the manual, it is not a surprise.

Mail is not configured from here. A run journal stays in the language of the run.

github.com/nessocrm/nessocrm

The manual is the docs folder of the repository. This site does not rebuild it.

The passage

Espo on one side. The external system on the other.

Nesso stands in the middle. It reads the channel, applies the mapping, and writes through Espo’s API. It does not open the CRM tables.

01

The external system

Not us

A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.

02

Nesso

This is us

Channel, sheet, fields. If the write switch is off, it does not write. If the field belongs to Espo, it does not clear it.

03

Espo

The sheet

The record, if it is born, is born there. CRM mail stays in Espo. The Advanced Pack is not rewritten.

Nesso always has Espo on one side. It is not a bridge between any two systems.

The product boundary