Tell us what your community tracks
What is the "thing" your community catalogs? Performers, venues, services, instructors, schools, vendors. One central entity is enough to start.
If you run a directory, a scene, or a network — comedians, weddings, schools, photographers, instructors, venues — and you're tired of renting it from Wix, Eventbrite or Instagram: a ceiba is your own node. Same data, same audience, infra you control, rules you write.
What is the "thing" your community catalogs? Performers, venues, services, instructors, schools, vendors. One central entity is enough to start.
We have working templates from existing ceibas. La Cartelera (live-comedy graph), Boda.market (wedding venues + vendors), Fotógrafos LATAM. Closest fit is your scaffold.
You bring the domain and any data you already have (CSV, spreadsheet, scraped list). We help you deploy under your domain. Your data stays yours, the graph layer is public, the product layer is yours to monetize or not.
The ceiba runs as a tiny FastAPI service — fits on a $5/month VPS. Your community claims their profiles. You decide what's free, what's paid, what's claimable, and what's owned by the commons.
Six communities live on the protocol today. Different shapes, same protocol.
Plus BotMarket (1841 AI agents, infra-type), Sociales.lat (social-dance scene), and Montessori MX (paused). Live list: /ceibas.json.
The rule: if the data would exist without your product, it belongs to the commons. If it only exists because someone used your product, it's yours.
Five live directories today. One (La Cartelera) is the gold standard. The others are seeds — real data but thin, no claim flow yet for most. If you start a ceiba in Q2-Q3 2026, expect rough edges and bring patience.
What does work: the protocol, the schema, the scaffold, the manifest, basic CRUD, llms.txt, MCP for agents. What's still landing: self-serve registration (Phase 3), one-click deploy buttons (Phase 2), karma economy in production.
Three lines — what you track, where it lives today, where you want it. We'll reply with the closest template and a 30-min deploy plan.
Write to [email protected]Are you technical and want to skip the email? Jump to → for developers.