Early accessBased in Phnom Penh
Requests, approvals and documents — out of Telegram groups and email, into one place.
Truostray helps Cambodian organisations manage conversations, requests, approvals and documents with clear ownership and an audit trail.
Already using Truostray? Sign in
- Free one-month pilot
- Setup and training in Khmer
- Our limits, published
Early access
We’re onboarding our first 10 organisations.
Get a free one-month pilot, setup and training in Khmer, and direct support from the team that built Truostray.
- A free one-month pilot, with one real process moved across
- Setup and training in Khmer, at your office or online
- Direct support from the team that built Truostray
01The problem
Work is everywhere.
Context shouldn’t be.
Teams talk in one place, track tasks in another, keep documents in a third and approve things in a fourth. Nothing is missing. The joins are.
- Conversation
in the chat tool
- Document
in the drive
- Task
in the tracker
- Approval
in somebody’s inbox
- Meeting
in another calendar
02The idea
A conversation should not be the end of the work
Follow one file through an ordinary week. It is the same file the whole way down — never re-uploaded, never re-attached, never emailed to four people who each keep a copy.
Conversation
“Can somebody approve this before Friday?”
Said in the channel where the work already lives, not in an email to four people.
Document
The file is attached where it was asked for.
Uploaded once, with its versions, its owner and the unit answerable for it. Not a second copy in a chat attachment store.
quotation.pdfattached hereTask
The message becomes something somebody owns.
With an assignee and a date — and it keeps the message, so the reason is still there in six months.
quotation.pdfApproval
It reaches the seat that signs, not a name that might have moved.
Quorum where a step needs two of three. Escalation when nobody acts. A delegate while somebody is away, deciding as themselves and on the record.
quotation.pdfMeeting
The hour it takes to settle it, in a room that was free.
Booked with the meeting rather than beside it, and given back on its own if the meeting is cancelled.
quotation.pdfDone
Approved, signed, and findable a year later.
With the decision, the document it produced, and the trail of who agreed to what — from which address and on which device.
quotation.pdfthe same file, all the way through
03The product
Not six products. Six things that know about each other.
Channels, direct messages, threads, huddles
What somebody now has to do
What the work leaves behind
Both of them end up needing a decision
The hour it takes to settle it
And the room it happens in
They know about each other because they share what is underneath
Six areas, one org chart, one set of permissions and one trail. Move somebody to a new post and the approvals waiting on that post stay with the seat, so the next person in it picks them up.
- Where you use it
- Web
- iOS and Android apps
- Room door sign
- Lobby board
- Six areas
- Chat
- Tasks
- Documents
- Approvals
- Calendar
- Rooms
- Shared by all six
- One org chart — units, seats, acting posts
- One permission model
- One audit trail
- One inbox, in-app and push
- Underneath
- Workspaces separated, checked at build
- A key per document
- Every session revocable
- Files stored in Singapore
The work doesn’t stop when you leave your desk
- Review
- Approve
- Respond
- Done
The same request, the same decision bar and the same trail on a tablet in a meeting or a phone in a car — with native apps for iOS and Android that carry the notification which gets you there.
Drawn, not photographed. We do not publish screenshots of a live workspace — the names and the numbers in one belong to whoever is using it.
04The philosophy
We believe work should feel connected
- 01Connected
- A conversation should not be the end of the work. Everything raised from a message keeps the message, so the reason survives alongside the thing.
- 02Simple
- Powerful without ceremony. Nothing here makes you raise a request to talk to somebody, and a team that only ever wants channels is using it correctly.
- 03Transparent
- People can see what is happening and where it has stopped. A request that is waiting on somebody says who, and an empty seat is a visible question rather than silence.
- 04Secure
- Workplace information deserves protection, and the security page says what we do not protect as plainly as what we do.
- 05Built for teams
- The org chart is underneath all of it. Work is addressed to a post rather than a person, so a transfer moves the authority and does not break the process.
Built with transparency
- Access control
- One workspace cannot see another, enforced by a check that fails our build.
- Role-based permissions
- Authority attaches to a seat in the org chart, so a transfer moves it with the post.
- Session security
- One-use refresh, every session showing its address and device, any of them revocable.
- Honest limitations
- A published list of what Truostray does not provide, and the control that stands in.