An orchestrator that keeps multiple state sources (server state, client state, local states) neatly synchronized without everything ending up in a global monster store. Ideal for larger apps, where states often exist side by side in an uncoordinated manner today.

1 stars 0 forks 1 watchers TypeScript Apache License 2.0
nextjs orchestrator react state-management
4 Open Issues Need Help Last updated: Aug 15, 2026

Open Issues Need Help

View All on GitHub
good first issue docs

An orchestrator that keeps multiple state sources (server state, client state, local states) neatly synchronized without everything ending up in a global monster store. Ideal for larger apps, where states often exist side by side in an uncoordinated manner today.

TypeScript
#nextjs#orchestrator#react#state-management
good first issue docs

An orchestrator that keeps multiple state sources (server state, client state, local states) neatly synchronized without everything ending up in a global monster store. Ideal for larger apps, where states often exist side by side in an uncoordinated manner today.

TypeScript
#nextjs#orchestrator#react#state-management
good first issue docs

An orchestrator that keeps multiple state sources (server state, client state, local states) neatly synchronized without everything ending up in a global monster store. Ideal for larger apps, where states often exist side by side in an uncoordinated manner today.

TypeScript
#nextjs#orchestrator#react#state-management
good first issue

An orchestrator that keeps multiple state sources (server state, client state, local states) neatly synchronized without everything ending up in a global monster store. Ideal for larger apps, where states often exist side by side in an uncoordinated manner today.

TypeScript
#nextjs#orchestrator#react#state-management