Privacy choices
This site may send the owner a minimal page-visit notice with page, browser, device type, and resolution. If you accept analytics, it can also remember an anonymous visit/session ID and collect richer engagement signals.
Read the privacy noticeBring up both services for local development: CMS on 3005, Alex OS on 8010.
The CMS and Alex OS are two separate processes that talk over HTTP. You need both running for the assistant/journey features to work; the CMS alone still serves the public site and admin.
Running CMS (port 3005) and Alex OS (port 8010) as separate processes is the minimum setup required for assistant and journey features to work locally.
What this covers
Two services, two ports: the CMS runs on 3005 and Alex OS on 8010. They communicate over HTTP. The CMS alone is enough to serve the public site and admin panel, but assistant and journey features require both processes running simultaneously.
Key takeaways
1. Start both services before testing any assistant or journey functionality — one without the other leaves those features broken. 2. The CMS and Alex OS are intentionally decoupled; understanding that boundary helps when debugging HTTP communication between them. 3. If you only need the public site or admin, the CMS alone is sufficient — no need to spin up Alex OS.