Morse Boards
// the work, where the work is discussedBoards, lists and cards for the work your teams are actually doing, running on your own infrastructure and signed in with the account they already have. Not another SaaS subscription with your delivery plan in it, and not a spreadsheet nobody updates. It sits next to the mail and chat where the work gets discussed.
You moved mail, chat and documents in-house. Then the delivery plan for all of it stayed in someone else's cloud, on a card-per-user subscription.
Morse Boards closes that gap. Projects, boards, lists and cards, on the same infrastructure and the same sign-in as the rest of the suite.
It is deliberately familiar. Anyone who has used a Kanban board before is productive in a minute, which matters far more here than novelty does.
Run it inside Morse Workspace alongside mail, chat and documents under one identity, or on its own if Boards is the only piece you need.
A board your team will actually keep up to date
Project tools fail on adoption, not features. This one is familiar enough to be picked up without training, and close enough to the day's work that updating it is not a separate errand.
Boards, lists and cards
- Projects hold boards; boards hold lists; lists hold cards. Drag a card and the state changes
- Labels to slice a board by workstream, risk or team
- Checklists on a card, for the steps that make up one piece of work
- Comments on the card itself, so the decision sits with the thing it was about
One door, the account they already have
- Sign in through your existing identity provider: no new account, no invite sprawl
- Users are matched on the address your directory already knows them by
- Access follows your directory, so leavers lose it when they lose everything else
- Served from your own domain, as an ordinary internal tool
Attachments on your own disk
- Drop a spec, an image, a PDF or a spreadsheet onto the card it belongs to
- Previews and thumbnails render in place, without a round trip to anyone's service
- Files live on your storage, under your backups and your retention policy
- Nothing is copied to a vendor's bucket to make the preview work
Unmistakably your toolWhitelabel
- Your name, logo and colours throughout, applied at run time rather than compiled in
- Right down to the browser tab, so it matches the rest of your estate
- Sits beside your other apps as one more thing the company provides
- Adoption is the point: a tool that looks like yours gets used
Sovereign, and straight with you about how
Every product in this suite protects data differently, because the job each one does is different. Here is exactly what Boards gives you and what it does not, so nobody discovers the shape of it during a procurement review.
Deployed how you deploy everything else
- On-premises, in your cloud, or fully managed by us
- Containers, your orchestration, your network, your certificates
- No phone-home, no vendor telemetry, no usage reported back to us
- Runs standalone, or inside Morse Workspace under one identity
One organisation cannot see another
- Per-tenant isolation: separate instance, separate credentials, separate database
- Sign-in is scoped to the tenant's own realm, not a shared user pool
- Board membership decides who sees a board, and it is enforced server-side
- Administrator rights are managed by you, not inherited from an outside directory claim
Encrypted in transit and at rest, not end-to-end
- This is a server-side application over a database, so the server can read the cards. Any Kanban tool that searches, sorts and filters your work is the same, whether or not it says so
- What that buys you is the ordinary protections done properly: TLS in transit, encryption at rest, and your own backups
- What it means is that whoever runs the server can read the boards. Self-host and that is only you
- If the content genuinely cannot touch a server, that work belongs in Morse Mail or Morse Mesh, which are end-to-end encrypted and where we do say so
Ready for the AI that is comingRoadmap
- Everything in Boards is reachable over a full REST API, so an assistant has a way in that is not screen-scraping
- Actions are attributable to a person through your identity provider, so what changed and who changed it is answerable
- The intent is Morse AI working across your boards: summarising a project, drafting cards from a thread, flagging what is stalled
- Stated as intent, not inventory: no AI features ship in Boards today
We would rather lose a deal on the third point than win one and have it surface later. If a board genuinely needs to be unreadable to the people running the server, tell us early and we will tell you honestly whether this is the right product for it.
What runs in your tenant
Four moving parts, all of them on your infrastructure. There is no fifth one sitting in someone else's cloud.
Deployable on-premises, in your cloud, or fully managed. No telemetry, and no usage reported back to us.
Where it's going
A board that works today, joined up with the rest of the suite next. What has shipped is on the left; we mark the rest as intent, not inventory.
Now
- Projects, boards, lists and cards, with labels, checklists and comments
- Attachments with previews, stored on your own volumes
- SSO sign-in through your identity provider, per tenant
- Whitelabelled throughout, applied at run time
- A full REST API over everything the interface can do
In progress
- Morse AI across your boards: summarise a project, draft cards from a thread, surface what has stalled
- Deeper suite integration: raise a card from a mail thread or a chat room without leaving it
- Reporting for people who need to answer where a project actually is
Your delivery plan, on your own infrastructure.
or fully managed.
Your identity, your database, your disk.