Hello, thank you very much!

Colanode is being built by me and @ylber-gashi, we're both senior software engineers who worked together for a long time. The long-term plan is to make Colanode the default collaboration tool and we're committed to keeping it open-source and build a community around it. Being production ready depends on the use cases and what users need, for some users it is ready now for other it might be once we release certain features. If you ask when we will release the first stable version (v1) we don't know yet. There are some things that we want to be certain that work and handle as much edge cases as possible, especially the sync engine, conflict resolution and data security. There are other major features we are planning to build such as mobile apps, sites for sharing publicly, integrations, automations, API etc, but that depends on user adoption and feedback.

About the data structure we are working on the documentation of Colanode where we'll also explain in details how it works. For now I can say that it's quite simple, we store almost everything the user creates in Colanode as a node with a type which can be a space, channel, chat, page, message, folder, file, database, record and others in future. Each of them have different attributes, for example a title, description, content for the message etc in JSON.

{
  id: "ulid",
  type: "page" | "message" | "file" | "database" | …,
  attributes: {
    parentId: "node_id",
    title: "string",
    content: "Yjs document",
    …
  }
}

I agree and we’re convinced, just like you, that many organizations need full data ownership. If you have any specific use case or idea in mind you can contact me at hakan[at]colanode.com and we can discuss in details.