Historical Wiki before documentation finalisation
Historical — superseded presentation, retained as evidence. The reviewed pages linked in the sidebar and the approved architectural roadmap control current status and sequencing. Old version milestones and access limitations below are historical, not current implementation or permission claims. Original Git history is also preserved.
Approved roadmap update — 8 September 2026: The architectural roadmap and migration record supersede earlier version-based scheduling and overlapping issue ownership below. Historical text/evidence is preserved. #49 has no architectural milestone; releases/deployments remain separate.
Tocyn (Welsh for "ticket") is an open-source helpdesk being developed into a feature-rich, multi-tenant application on the Cloudflare serverless edge.
Status: early development. The inherited application provides the starting point. Multi-tenancy and the roadmap below are development targets, not a claim that tenant isolation has been independently verified. There is no stable Tocyn release yet.
Tocyn is a fork of Luminatick by 05ng, retained under the MIT licence with the original copyright notice.
- Trying Tocyn
- Architecture and tenant isolation
- Deployment and operating costs
- Contributor guide
- Roadmap and releases
Questions and ideas belong in Discussions.
Reproducible bugs and agreed development tasks belong in Issues.
Report vulnerabilities through our private security reporting process.
Documentation improvements are welcome through pull requests. The versioned documentation in the repository remains authoritative.
The 8 September 2026 omnichannel roadmap adds cost-policy contracts in v0.1.0 and six dependent channel specifications in v0.3.0. See the accepted ADRs, #49 and #50. These are planned features, not production readiness claims; existing privacy/email objectives and deployment gates remain in force.
Begin with the contributor guide. Work in a development environment with synthetic data. Installation, local migrations and interface commands are documented there; a clean-checkout verification is tracked in issue #20.
Some inherited bindings contact remote services. Check configuration and potential charges before running integrations.
Choose a bounded issue, read its acceptance criteria and comment before starting substantial work. Documentation, accessibility testing, bug reproduction and code review are useful contributions even if you are new to Cloudflare.
The deployment guide currently describes inherited behaviour, including Resend. It is not evidence that the multi-tenant target is production-ready. Check the roadmap and security status before using the project with real customer data.
Approved roadmap update — 8 September 2026: The architectural roadmap and migration record supersede earlier version-based scheduling and overlapping issue ownership below. Historical text/evidence is preserved. #49 has no architectural milestone; releases/deployments remain separate.
The inherited code has an agent dashboard, customer portal, widget and Worker backend. Its configuration includes D1, R2, Durable Objects, Workers AI, Vectorize and Workflows.
Tocyn's direction is a Cloudflare-only application architecture with multi-tenant operation. A public project contact page using Web3Forms is separate from that application.
Tenant boundaries must be reviewed across authentication, membership, database reads and writes, storage keys, real-time events, background tasks, email, API keys and AI retrieval. A trusted tenant context must be enforced through each operation.
Issue #19 tracks the design and cross-tenant regression tests. This page does not claim those controls are already complete.
FidesLang work starts with an inventory of applicable data and processing boundaries. v0.1.0 targets majority coverage; v0.2.0 targets all applicable areas and optional end-user capabilities. Disabling those capabilities must not disable access control or tenant isolation.
The 8 September 2026 omnichannel roadmap adds cost-policy contracts in v0.1.0 and six dependent channel specifications in v0.3.0. See the accepted ADRs, #49 and #50. These are planned features, not production readiness claims; existing privacy/email objectives and deployment gates remain in force.
Approved roadmap update — 8 September 2026: The architectural roadmap and migration record supersede earlier version-based scheduling and overlapping issue ownership below. Historical text/evidence is preserved. #49 has no architectural milestone; releases/deployments remain separate.
There is no stable Tocyn release yet. The versioned roadmap is authoritative.
| Target | Intended outcome |
|---|---|
| v0.1.0 | Repository/security foundations, coding standards and majority FidesLang coverage |
| v0.2.0 | Complete applicable FidesLang coverage and optional end-user capabilities |
| v0.3.0 | Cloudflare-native email replacing Resend |
See open issues for work and acceptance criteria. These targets are not promised release dates.
Future release notes should state the exact version, delivered changes, known limitations, security fixes and migration steps. Audio/video, Signal and remote-support proposals remain subject to design and implementation work.
The 8 September 2026 omnichannel roadmap adds cost-policy contracts in v0.1.0 and six dependent channel specifications in v0.3.0. See the accepted ADRs, #49 and #50. These are planned features, not production readiness claims; existing privacy/email objectives and deployment gates remain in force.
Approved roadmap update — 8 September 2026: The architectural roadmap and migration record supersede earlier version-based scheduling and overlapping issue ownership below. Historical text/evidence is preserved. #49 has no architectural milestone; releases/deployments remain separate.
The application aims to make practical use of Cloudflare's free allowances and avoid server administration. Charges depend on workload, enabled services and current provider terms.
Follow the versioned deployment guide. It still uses inherited Luminatick resource names and Resend for outbound email. Cloudflare-native replacement is targeted for v0.3.0.
Before a real deployment, establish:
- Separate development and production resources and credentials.
- The service limits and usage controls for enabled integrations.
- Tested authentication email, replies and failure handling.
- Backup, restore, migration and rollback procedures.
- The security and tenant-isolation status of the exact version deployed.
These operational checks are work to complete, not guarantees supplied by an early-development repository. The public project's Web3Forms contact form is outside the application deployment.
The 8 September 2026 omnichannel roadmap adds cost-policy contracts in v0.1.0 and six dependent channel specifications in v0.3.0. See the accepted ADRs, #49 and #50. These are planned features, not production readiness claims; existing privacy/email objectives and deployment gates remain in force.
Approved roadmap update — 8 September 2026: The architectural roadmap and migration record supersede earlier version-based scheduling and overlapping issue ownership below. Historical text/evidence is preserved. #49 has no architectural milestone; releases/deployments remain separate.
Accepted 8 September 2026; implementation pending.
Tracking issue: #49. Start with #50 (v0.1.0 cost-policy contracts), then #51. All six omnichannel specifications target the existing v0.3.0 milestone; dates are not promised.
- #51 — v0.3.0: establish shared omnichannel ingestion and delivery contracts
- #52 — v0.3.0: extend tenant API and implement reliable signed outbound webhooks
- #53 — v0.3.0: implement tenant-owned Slack support channels
- #54 — v0.3.0: implement tenant-owned Microsoft Teams support channels
- #55 — v0.3.0: implement tenant-owned WhatsApp Cloud API messaging
- #56 — v0.3.0: implement tenant-owned Telegram support messaging
The four vendor issues carry help wanted; their integration depends on stable shared contracts. Enterprise API extensions and vendor adapters use the shared outbox independently.
Accepted ADRs. Preserve #18 Cloudflare email work, #19 tenant acceptance and #42 deployment gates; #48 governs UI primitives. Signal, LinkedIn, audio/video, RMM, centrally managed provider apps and WhatsApp templates are outside these six specifications.
- System-architecture
- Architecture-and-tenant-isolation
- Channels-and-conversation-model
- AI-and-autonomous-operations
- Architecture-decision-records