Business Platform · 2026
Worksuite
One Platform the Organisation Owns — 40 business modules delivered as a web app, a Windows and macOS desktop app and a public website, running on the client’s own servers.
- PHP 8.3
- CodeIgniter 4
- MySQL 8
- React 19
- TypeScript
- Tailwind CSS v4
- Electron
- Next.js
- LiveKit / WebRTC
- Docker
- Category
- Integrated Business Platform
- Client
- Enterprise Client (Self-Hosted)
- Duration
- 3 months (ongoing)
- Status
- In Development
Project Overview
Most growing companies end up paying for a dozen separate tools: one for files, one for mail, one for chat, another for invoices, another for HR. Each comes with its own user list, its own permissions and its own monthly bill, and the data sits with someone else.
Worksuite puts all of it in one place. Forty modules share a single login, one set of permissions and one search across everything, and the whole platform runs on servers the client owns. Each module can be switched on or off per team or per person, so an organisation only sees what it actually uses.
Flxware built every part in-house: the product design, the backend, the React web app, the Electron desktop app for Windows and macOS, the public website, the outside integrations and the server setup.
Key Features
- One login across all 40 modules
- Roles and permissions managed in one place
- File storage with versions, sharing links and recovery
- Word, Excel, PowerPoint and PDF editing in the browser
- Email, chat and video meetings built in
- CRM, invoicing, expenses, inventory and HR
- Desktop app for Windows and macOS with folder sync
- Two-factor sign-in and a full activity log
- Lost devices can be blocked or wiped remotely
- Search across files, mail, contacts and tasks
- Runs on the client’s own servers, with no per-seat fees
Challenges & Solutions
Challenges faced
- Keeping 40 modules separate without splitting up logins and search
- One backend serving a web app, a desktop app and a website
- Company files sitting on staff laptops
- Growing past one server without rebuilding everything
Solutions implemented
- A shared core holding one user list, one permission model and one search
- A single API and one shared design system behind all three
- Devices must be approved, and can be blocked or wiped remotely
- Storage and messaging sit behind swappable drivers