How it works

The same system, inside and outside.

The work you do inside your company and the work you do with other companies run on the same six parts — no bridge between them, nothing to integrate. Here is each one, in the order you meet it.

1

You join as yourself, or as your company.

Registration is open to anyone. Who you are on the network is one of three things, and the difference matters for everything that follows.

Members

Individuals who join under their own personal identity and take part in the community.

Organizations

Companies, which carry more weight and credibility on the network.

Employees

Accounts that belong to their organization. The organization owns the account and decides its permissions, including whether it can connect with people outside.
2

You connect across companies, not just inside one.

The tools most teams run on connect people inside a company, and every connection reaching outside it is gated by an administrator. We removed the gate: people find each other and connect directly, whoever they work for.

Nobody can ask their way into an organization, though — joining one is initiated by the organization, so there is no inbound queue to be flooded.

3

You install an app, or build one.

Applications run on the same foundation, with access to everything it offers. You install one once, for your side of it — and after that you can connect to anyone else offering the same app, with nothing new to install.

Or you build your own on top, and skip the identity, permissions and messaging you would otherwise write first.

How apps work

4

You decide who can reach you.

Openness without controls is a mailing list, so the two ship together. You choose which circles — your connections, your organizations, your project teams, or everyone — can start a conversation with you without asking first.

An employee account belongs to its organization, which sets its permissions, including whether it can connect outside at all.

5

Your conversations know what they are about.

A conversation can be linked to the record it is about — a person, an organization or a project — so the thread and the thing it concerns are not two separate places. And because the network already holds who people are and who they work for, keeping track of a relationship is not a separate system to maintain beside it.

6

Your clients arrive on your site, not ours.

An organization on Crossware can run its own client-facing site — its branding, its domain, its content — on the same network its team works in. The people who use it never see a platform; they see you.

Firms already do this — their clients sign in at their domain, see their brand, and never learn whose software is underneath.

Underneath all of it

One network, one identity, one set of permissions.

Every step above reads from the same foundation. That is the part you cannot build in an afternoon, and the part everything you do build starts from.

The network is the record

Who you are connected to, and who they work for, kept current by them rather than by you.

Everything else sits on it

Conversations, files, approvals and applications all read the same identities and the same permissions.

Try it on your own workflow.