head to head · open source
cap vs macro-tasks
cap has 24,271 GitHub stars, 2,234 forks, 339 open issues and last shipped yesterday. macro-tasks has 6,083 stars, 566 forks, 100 open issues and last shipped yesterday. cap leads on adoption by 299% (24,271 vs 6,083 stars). cap is written in Rust under a custom or non-standard licence; macro-tasks is written in Rust under AGPL-3.0. cap has attracted 9% as many forks as stars, macro-tasks 9%. macro-tasks was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| cap | macro-tasks | |
|---|---|---|
| GitHub stars | ★ 24K | ★ 6.1K |
| License | Custom / other | AGPL-3.0 |
| Written in | Rust | Rust |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 2.2K | ⑂ 566 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick cap if
- You weight community size — 24K stars and counting
- You want the Custom / other license terms
- Your stack matches Rust
- You value the larger contributor base for long-term maintenance
pick macro-tasks if
- You want the macro-tasks feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Rust
- You evaluated both and macro-tasks fits your workflow better
About cap
Cap Beautiful, shareable screen recordings. Open source, fast, and built for teams that want to own their data. Website Download Docs Pricing Discord Cap is the open source alternative to Loom. It gives you fast screen recording, polished local editing, instant share links, comments, transcripts, analytics, team workspaces, custom domains, custom S3 storage, and full self hosting when you need complete control. Use Cap for product demos, bug reports, onboarding, tutorials, design reviews, engineering walkthroughs, async standups, client updates, and any moment where showing the work is faster than scheduling…
About macro-tasks
Sign up · Docs · Book demo · Website · Feature requests · Contribute · Hiring Macro is the all in one workspace for you and your team. It unifies email + messages + docs + tasks + agents + CRM into a single fast interface with shared team level memory. Everything in your workspace is @linked and searchable so your team (and your agents) never have to switch tools. Why Macro We built Macro because we wanted a single operating system for our startup. There are many good software products, and we used them all — Slack, Linear, Notion, HubSpot, and Superhuman — but they don't work together as one system. As we…
read the full macro-tasks overview →
More in Miscellaneous
Related comparisons
Frequently asked questions
Is cap or macro-tasks more popular?
cap has 24,271 GitHub stars and macro-tasks has 6,083. cap has the larger community by that measure.
Are cap and macro-tasks free?
Both are open source. cap has no licence declared in this registry, and macro-tasks is licensed under AGPL-3.0. Both are free to self-host.
What is the difference between cap and macro-tasks?
cap is written in Rust and macro-tasks in Rust. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, cap or macro-tasks?
Choose cap if you want the larger community (24,271 stars) or its Custom / other licence terms. Choose macro-tasks if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.