staxsuite documentation
Choose a version
Version Other / archived
StaxSuite Product Requirements (PRD) #
Status: Draft for spec review · Owner: StaxDash studio.
Problem #
Individuals and small teams want a local-first office suite: files that remain theirs, work that does not require a cloud account, and predictable one-time licensing. The StaxDash studio already has functional desktop apps (StaxMD, StaxWord, StaxCode, StaxKB) and a launcher (StaxOffice). StaxSuite is the commercial umbrella that turns those into a shippable, licensed, paid product family while keeping a free launcher entry point.
Target users #
- Individual and small-team productivity users who prefer desktop applications over web SaaS.
- Privacy-conscious users who need local-first editing without telemetry.
- Existing StaxOffice users upgrading from the free launcher to paid modules.
Solution overview #
StaxSuite groups the four tools under one commercial product. StaxOffice remains the free launcher; each module is licensed separately or in bundles through StaxStore. Edition gating lets users install the free launcher and unlock paid modules as needed, all local-first.
Repository structure decision (changed in planning) #
The tools originally lived as modules inside a single large StaxOffice
repository. That design was a fun concept but not practical to expand: every
change touched one giant tree and one app’s release blocked the others. The
suite was therefore split into independent repositories, each with its own CI,
versioning, and release cadence, tied together by the StaxSuite umbrella and a
suite.toml manifest. This is the current shape:
StaxDash/StaxOffice— free launcher (staxoffice)StaxDash/staxmd— Markdown editor (staxmd)StaxDash/staxword— word processor (staxword)StaxDash/staxcode— code editor (staxcode)StaxDash/staxkb— kanban board (staxkb)StaxDash/staxsuite— umbrella manifest + install helper
MVP scope (in-scope) #
- Independent, tested repositories for each app (done)
- StaxOffice launcher dispatching to the installed apps by command (done)
- StaxStore integration for edition gating and licensing
- Persistence layer, recovery, and packaging that the prototypes lack
- One-time, local-first licensing (no mandatory cloud account)
Out of scope (MVP) #
- Cloud sync as a requirement (optional future tier at most)
- Document-format compatibility promises beyond documented scope
- Mobile platforms
Monetization #
Free launcher + paid modules/bundles via StaxStore; proprietary EULA retained. Detailed in the licensing policy and StaxStore stack.
Timeline #
Specified under Phase 3 of the organization roadmap; build begins in Phase 4.3 (split into independent projects).