head to head · open source

cap vs macro-tasks

cap has 22,381 GitHub stars, 1,918 forks, 339 open issues and last shipped yesterday. macro-tasks has 4,345 stars, 416 forks, 100 open issues and last shipped yesterday. cap leads on adoption by 415% (22,381 vs 4,345 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 10%. 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.

cap ★ 22K macro-tasks ★ 4.3K category Miscellaneous

← all 8884 open source comparisons

Side by side

cap macro-tasks
GitHub stars ★ 22K ★ 4.3K
License Custom / other AGPL-3.0
Written in Rust Rust
Last push 2026-09-17 2026-09-17
Forks ⑂ 1.9K ⑂ 416
Self-hosting Yes Yes
Data ownership Your server Your server

pick cap if

  • You weight community size — 22K stars and counting
  • You want the Custom / other license terms
  • Your stack matches Rust
  • You value the larger contributor base for long-term maintenance

full cap profile →

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

full macro-tasks profile →

About cap

Cap open source screen recording sharing project for teams. Lives web desktop software ecosystem. Uses Rust TypeScript stack, Next.js web dashboard, desktop apps macOS Windows. Presents alternative Loom. Supports importing existing Loom videos.

read the full cap overview →

About macro-tasks

Macro is an open source unified workspace named macro tasks, built in Rust and SolidJS under AGPL 3.0. It brings email, messages, docs, tasks, canvas, agents, calls, files, pull requests, and CRM into one web interface. The project lives in the Rust and SolidJS web ecosystem, with GitHub topics such as agent, ai, mcp, messaging, notes, notion, crm, email, and linear.

read the full macro-tasks overview →

More in Miscellaneous

firecrawl ★ 182K Godot ★ 117K Home Assistant ★ 91K OpenCut ★ 90K OpenBB ★ 73K Jellyfin ★ 57K

Related comparisons

firecrawl vs cap firecrawl vs godot godot vs home-assistant firecrawl vs gdevelop firecrawl vs monogame firecrawl vs sbox godot vs gdevelop godot vs monogame godot vs sbox firecrawl vs home-assistant firecrawl vs cratedb firecrawl vs gladys-assistant home-assistant vs opencut godot vs cratedb godot vs gladys-assistant home-assistant vs cratedb opencut vs cratedb firecrawl vs novu firecrawl vs postiz firecrawl vs openseo firecrawl vs keploy firecrawl vs parlant firecrawl vs crm firecrawl vs hanko

Frequently asked questions

Is cap or macro-tasks more popular?

cap has 22,381 GitHub stars and macro-tasks has 4,345. 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 (22,381 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.