Process Compose is a simple and flexible scheduler and orchestrator to manage non-containerized applications.
Topics
Jump into the topic listings this repository belongs to.
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Jul 19, 2026
Current11
Previous13
Weekly star gains
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
44 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 19, 2026
Current2,576
Previous2,565
Cumulative total
Running total of the GitHub GraphQL stargazer count over time (not weekly deltas), reconstructed from starredAt events and totalCount in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
44 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Join the conversation
Share what you know about process-compose — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting process-compose.
Project Q&A
Browse implementation threads tied directly to F1bonacc1/process-compose. Each question links through to the full answer page.
Be the first to ask how teams run process-compose in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses process-compose — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post