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 comparison

It is not a second CRM and it is not a query.

A script copies cells. It does not know who owns the field, it does not ask before closing, it does not tell an expected file from a file already read.

Espo on one side

An Espo table is not an API.
Three ways to get it wrong

A script

A script reads the CSV and runs an INSERT. The next day the file has one row less and the script deletes, or it leaves the record and nobody knows the source no longer has it. There is no preview. There is no hash, so it rewrites even what did not change.

If the salesperson's note sits in the same table, the script clears it when the cell arrives empty. It has no field owner.

A query on the tables

Writing on Espo tables skips the checks, the teams, the history, and the hooks. The day Espo changes a schema, the query is the first piece that breaks, and it breaks quietly.

Nesso talks to Espo only over HTTP. The key, the team, and the close go through the API. The Espo database is not a channel.

A second CRM

Keeping the masters in another product and then chasing them in Espo doubles the truth. Nesso is not that second place. It always has Espo on one side. The other side is a channel: a file, a SELECT, a call.

The recipes for accounts, contacts, sites, and the price list are a mapping to review. They are not a certified connector and they do not replace the ERP.

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