Cloud

The hosted part of the Curate Labs stack is GraphForge Hub, at graphforge.sh. It does one job: it gives a GraphForge project a stable identity on the internet, so you can publish it, share it, and clone it from anywhere.

What Hub does

• A stable address for a graph. Each published project gets a repository page with its summary, versions, and previews.
• Publish and clone from the tools you already use. gf publish sends a project up. gf clone brings one down. Python and Node reach the same commands.
• Discovery. Browse public graph repositories and clone the ones you want to question or build on.
• Versions you can cite. Published versions are immutable and digest-addressed, so a graph referenced in a report stays the graph that was referenced.

What Hub deliberately does not do

Hub runs no GraphForge computation. Queries, analysis, and extraction happen in your own process, on your own machine or server. The Hub stores the project bytes GraphForge produces and renders pages from the summaries GraphForge generates. If your documents cannot leave your environment, nothing about Hub requires them to.

Status

Hub is live for public repositories, and gf clone and gf publish are part of GraphForge today. Private spaces for teams and organizations, with access control and billing, are in development. If you want one early, tell us what you would use it for.

Verdant is not offered as a hosted service, by design. It stays self-hosted so documents never leave your environment. If you want Verdant run for you inside your own cloud account, that is a services engagement.

How the three offerings fit

• Open source is the code: GraphForge and Verdant, free to run anywhere.
• Cloud is distribution: Hub gives the graphs you build a place to live and a way to share them.
• Services is help: we build the pipeline with you, and you keep it.

Next steps

• Visit graphforge.sh and browse public repositories
• Read about publishing and portable projects in the GraphForge docs
• Talk to us about private spaces