Introduce the ability to host users EventCatalog - one-command deploy

[boyney123]

Use Case

Teams using EventCatalog today need to self-host their catalog — setting up infrastructure, CI/CD pipelines, auth, and preview environments. This is friction that slows adoption, especially for teams that just want to share their catalog internally without managing infrastructure.

Proposed Solution

EventCatalog Cloud — a managed hosting platform for EventCatalog.

The workflow would be:

1. Get an API key from EventCatalog
2. Run eventcatalog deploy from your project
3. Your catalog is live at acme.eventcatalog.app (or similar)

That is it. No infrastructure to manage, no CI/CD to configure.

Features we are exploring

Feature	Description
One-command deploy	eventcatalog deploy builds and publishes your catalog
Custom subdomains	your-org.eventcatalog.app
Private catalogs	Authentication required to view — only your team can access
PR previews	Automatically deploy preview URLs for pull requests so reviewers can see changes before merging
Custom SSO	Integrate with your existing identity provider (Okta, Azure AD, etc.)

What we want to understand

We are gauging interest before committing to this direction. If this is something your team would use, please:

1. 👍 this issue to signal interest
2. Comment with answers to any of these:
   • Would a hosted option unblock adoption for your team?
   • Which features matter most to you (private catalogs, PR previews, SSO, something else)?
   • Are there dealbreakers (e.g., data must stay in a specific region, on-prem only)?
   • What would you expect to pay for something like this?

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.
• If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.

[cfranzen]

Definitely interesting, especially when you have many tiny teams. We have a event driven architecture distributed over several teams. Each team is documenting their part of the system in their own EventCatalog. But they don't want to host it by themselves. We are not doing federation yet, but we will and that would be a killer feature if it would be combined with a managed solution. So each team could do a npm run federated-deploy and it would magically merge the changes from that team into a shared federated EventCatalog instance that is managed for them.

If you offer a managed service, please host it in Europe, in the best case with a non-US company. As soon as a US company or even a US datacenter is involved, compliance processes are a nightmare.

[boyney123]

Thanks @cfranzen , yeah I see a interesting usecase here for federation too, love that idea.

Federation is an interesting thing, as it was once built (over a year , maybe two ago), and not really come back to the design of it yet, and I feel there is so much we can improve on federation tbh.

The hard part I try to figure out is how to you document your internal things (team things) whilst you depend on other things, at the moment federation requires you to mock things out.... but I wonder if there is a better way?

Yeah I think the ability to host in Europe/US would have to be an option for sure.

[crognon]

That would be awesome.

Some feature could be to be allowed to choose cloud provider (A I asking too much here ?)

The Catalog Federation could be a super thing to grow

[boyney123]

Hey @crognon

Any idea how you would see the federation working here for you and your team?