Anil-matcha/open-spaces

Free, open-source alternative to ChatGPT Spaces: a self-hostable AI workspace for shared pages and conversations.

View on GitHub ↗Jump to charts ↓Open shareable report →

Anil-matcha/open-spaces has 900+ stars and 200+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 22 minutes ago
Added to GitGenius on October 13th, 2026
Created on October 12th, 2026
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 200
Total Stargazers: 921 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 54.3 days
Mean response time: 353.3 days
90th percentile: 805.7 days
Tracked items: 40

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 1
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 1

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Open Spaces is a self-hostable AI workspace that provides a free, open-source alternative to ChatGPT Spaces.

The tool addresses the need for a collaborative AI workspace that users can run on their own infrastructure. It combines shared pages, conversations, and AI-powered tools into a single workspace environment. The approach centers on organizing work into Spaces containing pages and conversations, with a rich-text editor that supports inline AI actions, image generation, and chat capabilities powered by configured AI providers like MuAPI.

Open Spaces suits teams or individuals who want to avoid vendor lock-in and prefer to self-host their AI workspace infrastructure. It works well for organizations that need to keep data on their own servers, customize the application for specific workflows, or integrate with particular AI providers. The project is still under active development, and the README explicitly warns that authentication and per-Space authorization are not yet consistently enforced across API routes, making it unsuitable for multi-user deployments with sensitive data until those security boundaries are implemented and reviewed. The current WebSocket implementation does not support collaborative editing, and agent execution and meeting transcription workflows remain incomplete.

Issues and pull requests in the project often wait weeks or longer for a first response.