Tasks, chat, docs, meetings and dashboards that share one set of people, one set of permissions and one search box. Not five subscriptions pretending to integrate.
No credit card to startYour own address in a minuteImport from what you use now
In the box
Not six apps behind one logo. The same people, the same Spaces and the same permissions run through all of it, which is why a task can be discussed in a channel, explained in a doc and reported on in a dashboard without being copied anywhere.
Lists, boards, calendars and timelines over the same tasks — a view is a lens, not a copy. Fifteen field types, task types of your own, and an activity log on every task that says who changed what.
Channels for the team, direct messages for two, threads on anything. Mention a task, a doc, a Space or a person and the reference resolves live — hover it and you get the real thing, not a dead link.
A library that lives in the same tree as the work. A doc belongs to a Space, carries the same labels as the tasks around it, and opens beside the thing it explains.
Calls that start from a task, a channel or the calendar. Ring the people who need to be in it, share a screen, chat in the call, and the record of it lands back where it started.
Cards computed on the server from one catalogue, arranged in whatever order tells your story. Private to you until you decide otherwise, then shared with exactly who should see them.
When this happens, do that — on statuses, assignees, labels and dates. Public forms feed straight into a list, and the person filling one in never needs an account.
All of it, included
There is no chat licence, no reporting add-on and no integration to configure. Turn on what your team needs and hide the rest — the workspace only shows what you have asked for.
The tree your work already has a shape like.
One set of tasks, seen four ways.
A bug is not a story. Say so.
Fifteen types, with a real editor for each.
Rename one everywhere, or in one Space.
Every edit, with who and when.
The audience for a task, decided per task.
Public rooms with a handle people can type.
Open to everyone in the workspace.
Seven kinds of thing, one @ picker.
Filtered five ways, favourited in one click.
For the part of the plan that is not a list yet.
Ring, join, record, and keep the thread.
Read your calendar in; publish an ICS feed out.
Computed server-side, ordered by you.
Rules you can read back in plain English.
A link anybody can fill in, answers into a list.
The preview is the plan. Nothing lands unseen.
A closed catalogue of actions, not a firehose.
Four roles, narrowed per Space and per project.
Save a workspace, apply it to the next one.
Primary and Other, and nothing shouts twice.
On any account, nudged for the rest.
acme.1workspace.in, with its own certificate.
Why one workspace
Work does not live in any one of them. It lives in the gaps between them — the decision made in chat that never reached the task, the doc nobody could find, the status that was true on Tuesday. No integration puts that back.
Your address
Every workspace lives on its own hostname. Bookmark it, put it in the onboarding doc, hand it to a new starter — it is the only URL anybody needs to remember.
Nobody has to pick a workspace after signing in. The address is the workspace, so two teams on one laptop never end up in each other’s.
Not a shared wildcard. Your workspace’s hostname is never served under anybody else’s name, and the certificate renews on its own.
Change the address and the old one keeps working — every link already sent, in every email and every doc, still lands in the right place.
Trust
The boring half, which is the half that matters once more than four people are in here. All of this is in the product today, not on a roadmap.
Every table that holds your work is scoped to your workspace, and deleting the workspace deletes what is in it — no orphaned rows left behind under someone else’s name.
Four workspace roles, overridden per Space and per project, and private Spaces that stay private — membership decides, never the hostname somebody typed.
Every action from a closed catalogue, recorded with who did it, when, and in which workspace. Filterable, and visible to the people entitled to see it.
Time-based codes on any account, with a nudge for anyone who has not turned it on yet.
A certificate issued for your workspace’s own hostname, on demand rather than by wildcard, renewed without anybody thinking about it.
A full export of tasks, docs, messages and files. The importer that brought your work in runs in reverse.
Questions
Including the two nobody puts on a marketing page: what it costs, and how you get your work back out again.
It is one application that carries tasks and projects, team chat, docs and wikis, video meetings, dashboards, automations and public forms. They share one set of people, one permission model and one search box, so a task can be discussed in a channel, explained in a doc and reported on in a dashboard without being copied anywhere or synced by an integration.
Those are project tools that integrate with a separate chat app and a separate meeting tool. In 1Workspace the chat, the calls and the docs are the same product as the tasks, which is why a mention resolves live rather than pasting a link, and why one permission change applies everywhere at once. Each workspace also gets its own hostname — yourteam.1workspace.in — instead of a workspace picker after login.
No. Import brings in tasks, lists and members from a CSV or from the tool you use now, and the preview is the plan: you see exactly what will be created before anything is written, and nothing lands unseen. Teams usually move one Space first and keep the rest where it is until they are ready.
You can create a workspace and start using it without a credit card. Pricing for larger teams is not published yet — when it is, it will be on this page rather than behind a sales call.
Yes, and it is a feature rather than a favour. A full export covers tasks, docs, messages and files, and the importer that brought your work in runs in reverse. Deleting a workspace deletes what is in it rather than leaving orphaned rows behind.
Every table that holds your work is scoped to your workspace. There are four workspace roles, overridden per Space and per project, private Spaces that stay private, time-based two-factor authentication on any account, a complete audit log of a closed catalogue of actions, and a TLS certificate issued for your own hostname rather than a shared wildcard.
Every workspace lives on its own hostname, like acme.1workspace.in. Nobody has to pick a workspace after signing in, two teams on one laptop never end up in each other’s, and it is the only URL a new starter has to remember. Rename it and the old address keeps working, so links already sent in emails and docs still land.
About a minute to create the workspace and choose its address. From there you can start from a template that lays out Spaces, lists, statuses and fields for how your team works, invite the people who need to be in it, and fill in the rest as you go.
They cover the same daily work: public channels with handles, direct messages open to everyone in the workspace, threads, mentions that resolve to the real task or doc, and calls with screen share, recording and in-call chat that start from a task, a channel or the calendar. Chat history can be imported from Slack, and the preview shows what will be created before it is.
A public form is a link anybody can fill in with no account, and the answers land straight into a list with the questions they were asked. Calls can be joined by the people invited to them.
Create it, choose your address, invite whoever needs to be in it. Bring your current work with you, or start from a template and fill it in.
No credit card to startImport from a CSV or your current toolDelete it just as easily