Skip to content

Uniffy workspace overview

Uniffy is one workspace for the things you would normally keep in five apps. Notes, files, chat, projects, calendar, AI agents. They live next to each other, and you can reference any piece of content from anywhere with an @ mention.

Uniffy works for one person keeping their own life in order, a few friends sharing things securely, a small team, or a large company. Same product, same code, regardless of how many of you there are.

These docs exist so that you can verify all of that for yourself, decide whether Uniffy fits the way you work, and get unstuck when something breaks.

The docs are split into four guides. Each one is written for a different reader.

Principles explains the rules we will not bend on: one codebase for cloud and self hosted, two admin surfaces by design, and no phone home, ever. Read this first if you are evaluating Uniffy against another tool, because the real differences usually live here.

User Guide is for everyone who opens the app on a normal day. It covers notes, files, chat, mentions, agents, calendar, and how the product feels in use.

Administration Guide is for org owners and admins. It holds the settings that decide how your tenant behaves: members, permissions, SSO, the audit log, encryption.

Deployment Guide is for the operator running Uniffy on their own hardware. Install, configure, upgrade, back up. It also lists every setting Uniffy reads at startup and what each one does.

Pick the path that matches you.

You just signed up and want to learn the product. Open the app and click around. The app is the best place to learn how Uniffy feels. Come back here for the parts that are not self evident.

You are evaluating Uniffy for your team. Read the Principles page. Then read the FAQ and the pricing on uniffy.io. You will know in five minutes whether we are aligned with how you want to work.

You are about to run Uniffy on your own servers. Start with the Deployment Guide. It covers the bring up from first install through day two operations.

If something in these docs is wrong, unclear, or out of date, open an issue on GitHub. The docs ship from the same repo as the product. A fix to a page lands the same way a fix to a button does.