The thing that makes NearSync different from a suite of connected tools is not a feature. It is that there is one database behind every department.
What That Means
Sales, Finance, People, Operations, Marketing and the rest are surfaces onto the same data, not separate products exchanging copies.
A contact is one row. Sales sees it as the person on a deal, Finance as the party on an invoice, Support as the customer on a ticket. Nothing syncs, because nothing is duplicated.
The Seam You Do Not Have
Most stacks are joined by integrations, and every integration is a seam where things go wrong in the same predictable ways:
- Sync lag. The other system is right; this one is right in an hour.
- Field mapping drift. A field added in one place never appears in the other.
- Two sources of truth. Both systems have a customer record, and they disagree.
- Identity resolution. The same person exists twice with different ids.
None of those exist between two NearSync departments, because there is no boundary to cross. The consequences are concrete: a deal's totals are already on the invoice; a call is on the deal timeline without anyone copying it; commission on a won deal becomes a payroll line.
The seams still exist at the edges - between NearSync and Google, Meta, your bank. Those are integrations and behave like integrations.
Organisations, Hubs, Departments
Three levels, and they answer different questions:
| Level | Answers |
|---|---|
| Organisation | Which workspace is this? The outermost boundary. |
| Hub | Which legal entity? Currency, tax, invoice numbering, working week. |
| Department | Which team? Routing, approvals, ownership. |
A record belongs to one organisation, usually one hub, and typically one department. Access narrows down that structure rather than being listed per person.
Access Is Enforced In The Database
Not in the interface. Every query is filtered by the same rules regardless of which screen issued it, which is why hiding something in the UI is never how access is restricted here. See How Your Data Is Protected.
Configuration, Not Code
Tenants differ by configuration rather than by having different software. Custom fields, pipelines, stages, roles, leave types, approval thresholds and branding are all data.
That is why a change to your setup is immediate and does not wait for a release, and why two workspaces running very differently are running the same code.
What Runs In The Background
Scheduled work runs continuously - leave accrual, attendance close-off, overdue checks, reminders, automation ticks, channel syncs. It is why balances are current when you open them rather than calculated when you ask.
Common Questions
Is our data mixed with other customers'? On managed hosting the database is shared and separated by enforced rules. On self-hosted it is your own database entirely. See Managed or Self-Hosted.
Does one department slow another? They are surfaces on the same data, not competing systems.
Can we use only part of it? Yes. Turn on what you need; the rest is not in your way.
What if we outgrow it? Your data is exportable in a standard format at any time. See Getting Your Data Out.
Did this answer your question?
No, ask a person