01
In development
NowCore content layer — SDK, backend, docs. No public customer access yet.
- SDK, overlay, marking (primitives & components)
- Dashboard, auth, draft/live foundations
- Docs, OpenAPI, and agent discovery in parallel
Roadmap
Where we are
Right now: In development. Next: Private Beta, Early Access, v1, community feedback, and v2. No fixed calendar dates — quality over deadline promises.
- 01In development
- 02Private Beta
- 03Early Access
- 04v1 release
- 05Community feedback
- 06v2
02
Private Beta
PlannedSelected testers with real sites. Feedback on editor, stability, and onboarding — not mass rollout.
- Invites for agencies / developers with concrete use cases
- Expectation: software still unfinished
- Prioritization driven by real-world usage
03
Early Access
PlannedLimited, broader access before official v1 — via the waitlist, in waves.
- Waitlist / soft open (no unlimited self-serve launch)
- More stable onboarding (including setup CLI) and documented paths
- Feedback from more real sites before the v1 cut
04
v1 release
PlannedFirst publicly usable version with a clearly scoped feature set — content layer first.
- Defined feature cut
- Documented integration paths
- Transparent operating model before launch
05
Community feedback
PlannedAfter Early Access and v1, learn systematically — what is missing, what waits intentionally.
- Integration and UX feedback
- Priorities for the next release cut
06
v2
PlannedExpansion based on beta, Early Access, and community input. Scope stays open — no feature list as a promise.
- Depth where real usage demands it
Horizon
Website management platform
Macrocontent is the entry point — not “another CMS”. Long term: content + SDK first; then optionally hosting, analytics via the SDK on the real page, and an internal database for structured records alongside page content. All of that only after a convincing content core.
Early Access is not open yet — until then, join the waitlist, read the docs, and follow this roadmap.