← Back to AI Insights
Gemini Executive Synthesis

CraftHub, a generalized collaboration core for the "Craft" application family, addressing account-based collaboration, permissions, and team management.

Technical Positioning
Unified, account-driven collaboration platform with backwards compatibility, enhancing the "Craft" family's market competitiveness.
SaaS Insight & Market Implications
This discussion outlines a strategic initiative to integrate CraftHub, a critical collaboration layer, across the "Craft" application family. The current state of "individual tools" lacking account-based collaboration, permissions, and team features is identified as a "beta blocker" and a significant market gap. CraftHub aims to provide this missing functionality, leveraging a robust, backwards-compatible collaboration protocol. The proposed adoption and ownership transfer from a personal project to the `storytold` organization signifies a move towards formalizing and scaling this crucial capability. Market implications are substantial: successful integration of CraftHub will transform the "Craft" suite from disparate tools into a cohesive, enterprise-ready collaborative platform, directly addressing a core competitive weakness and unlocking new market segments requiring advanced team functionalities. The technical handover process itself reveals organizational friction points.
Proprietary Technical Taxonomy
CraftHub collaboration without accounts accounts, teams and permissions sync and sharing preview beta blocker generalized collaboration core craft-collab figcraft-collab

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Oct 14, 2026
Repo: storytold/figcraft
CraftHub: closing gap (collaboration without accounts) — a decision brief for the administrators

## The one paragraph

The family is fourteen world-class apps, each clean, independent and privacy-complete — and today a **set of individual tools**: collaborating means emailing files, selling means no marketplace exists, and anyone without a powerful machine (or unwilling to install) is excluded entirely. Your own docs record the gap: `collab-protocol.md` names its unexecuted step six as *"Accounts: people signing in, per-person permissions, teams and projects"* — the structure is ready; the missing layer is accounts, teams and permissions above it. `docs/gaps.md` ranks **"sync and sharing preview, without accounts"** as gap #2, a *beta blocker*.

**CraftHub is that layer** — built over the protocol this repository already proved, with literal backwards compatibility (a v2 client keeps working against a v3 server with its full current behaviour; new messages ride feature words, exactly how v2 itself grew four times).

## What is delivered today

- **[hasan-sdaif/crafthub](github.com/hasan-sdaif/craft... — the reference implementation, proposed for adoption: the generalized collaboration core (`craft-collab`, ported from `figcraft-collab` with its property tests: fractional indexing, server-ordered LWW with refusal fixes, per-user undo, join codes, the RGA text property, the three-way merge, the per-seed convergence simulator), protocol v3 shapes, identity/authz (64 capabilities × 8 roles, tested cell by cell), teams, review, comments, notifications, assets, BYO-...

Developer Debate & Comments

hasan-sdaif • Oct 15, 2026
**The handover: CraftHub becomes the org's, and my review queue gets small.** A fair concern was raised — in review threads and elsewhere: CraftHub as presented linked every app back to my personal GitHub, it was never discussed before the PRs arrived, and the queue from me is far too big. All three are true. This comment is the structural fix, not a debate. **1. The org owns CraftHub — here is the mechanism.** I attempted the direct repository transfers today (`hasan-sdaif/crafthub`, the reference implementation, and `hasan-sdaif/craftmarket`, the §22 web scaffold). GitHub refused both — because your org, correctly, does not allow outside accounts to create repositories in it. So the handover needs one action from an owner, in whichever form you prefer: - **You create `storytold/crafthub` (and `storytold/craftmarket`, if the platform is wanted at all), and I open one PR per repo containing the entire code for your review.** You read every line before it becomes yours, and you own t...
tanish2k09 • Oct 15, 2026
Thanks, I have created a blank /crafthub repo. I will leave the /craftmarket decision open for now.
hasan-sdaif • Oct 15, 2026
@tanish2k09 — thank you for creating `storytold/crafthub`. That's the action the handover needed, and I'll meet it from my side exactly as proposed: **The platform code arrives as one PR into `storytold/crafthub` — the whole tree, for line-by-line review, the moment you say go.** The branch is ready; one word from you and it's open today. Nothing of it touches any app repo: no adapter depends on it, no app changes, until the org reviews and decides. And I want to say the next part plainly, because @wdunn001's CollabCraft picture on storytold/craft-libs (posted within the same hour you created the repo) is the most important input the org has: **CollabCraft is the deployed host today, and nothing I propose displaces it.** The crafthub PR, when it opens, carries that framing in its first line — the platform arrives as reference code the org controls outright: adopt it, adapt it, or archive it, whichever the maintainers and CollabCraft's author judge right for the family. The CRDT c...
hasan-sdaif • Oct 15, 2026
**The ownership transfer is done from my side — one mechanical step needs an owner.** @tanish2k09 — the repo you created is exactly the home this needs, and I went to move the code in as agreed: one PR, the whole tree, for line-by-line review. One mechanical thing blocks it, and it's GitHub's rule, not the org's: **GitHub refuses to fork an empty repository** (403: "Empty repositories cannot be forked"), and a cross-repo PR needs a fork. The smallest unblock is either of: - **any initial commit on `storytold/crafthub`** — a one-line README is enough. The minute it lands I fork, push the full 19-commit history, and the review PR is open. - **or temporary write access for me** — I push a review branch and open the PR inside the repo itself. Both arrive at the same review gate; the first asks for less trust. **What is already done from my side:** both personal repositories — `hasan-sdaif/crafthub` and `hasan-sdaif/craftmarket` — are **deleted**. Nothing of CraftHub lives on my account...
tanish2k09 • Oct 16, 2026
Placeholder README created in the crafthub repo. It should be greenlit.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from storytold/figcraft.

Extracted Positioning
Popover UI element behavior during text editing.
Stable and predictable user interface experience across operating systems.
Top Replies
ticket-craft[bot] • Oct 15, 2026
Possible duplicate of .
foziaiiiiiiiiii-ui • Oct 15, 2026
Looks. Very Interesting. And quite Funny.
vxMacDev • Oct 16, 2026
I'm working on this (and , which looks like the same bug): I'll reproduce the "…" text options popover growing on Windows and keep its size fixed as the pointer moves in and out. PR soon.
Extracted Positioning
Authentication for the application's control channel.
Secure inter-process communication and remote control, consistent with family-wide security standards.
Extracted Positioning
File system access control for MCP (Multi-Craft Protocol) tools.
Secure and confined file operations, consistent with other Craft family applications.
Extracted Positioning
Rendering of visual effects (glass, blur) and overall workspace performance.
High-performance, visually rich design environment.
Extracted Positioning
Figma file import functionality.
Robust compatibility and performance for large design assets.

Frequently Asked Questions

Market intelligence mapped to CraftHub, a generalized collaboration core for the "Craft" application family, addressing account-based collaboration, permissions, and team management..

What problem does CraftHub, a generalized collaboration core for the "Craft" application family, addressing account-based collaboration, permissions, and team management. solve?
Based on our AI analysis of the original developer request, its primary technical positioning is: Unified, account-driven collaboration platform with backwards compatibility, enhancing the "Craft" family's market competitiveness.
How is the developer community reacting to CraftHub, a generalized collaboration core for the "Craft" application family, addressing account-based collaboration, permissions, and team management.?
Yes, we have tracked 5 direct responses and active debates regarding this specific topic originating from GitHub Issue.
What architecture is tied to CraftHub, a generalized collaboration core for the "Craft" application family, addressing account-based collaboration, permissions, and team management.?
Our proprietary extraction maps CraftHub, a generalized collaboration core for the "Craft" application family, addressing account-based collaboration, permissions, and team management. to adjacent architectural concepts including CraftHub, collaboration without accounts, accounts, teams and permissions, sync and sharing preview.

Engagement Signals

5
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like CRDT and CraftHub by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.