head to head · open source

OpenCut vs PermissionsKit

OpenCut has 97,156 GitHub stars, 9,671 forks, 378 open issues and last shipped 1 months ago. PermissionsKit has 5,811 stars, 479 forks, 4 open issues and last shipped 2 months ago. OpenCut leads on adoption by 1,572% (97,156 vs 5,811 stars). OpenCut is written in TypeScript under MIT; PermissionsKit is written in Swift under MIT. OpenCut has attracted 10% as many forks as stars, PermissionsKit 8%. OpenCut 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.

OpenCut ★ 97K PermissionsKit ★ 5.8K category Miscellaneous

← all 20902 open source comparisons

Side by side

OpenCut PermissionsKit
GitHub stars ★ 97K ★ 5.8K
License MIT MIT
Written in TypeScript Swift
Last push 2026-09-24 2026-09-12
Forks ⑂ 9.7K ⑂ 479
Self-hosting Yes Yes
Data ownership Your server Your server

pick OpenCut if

  • You weight community size — 97K stars and counting
  • You want the MIT license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full OpenCut profile →

pick PermissionsKit if

  • You want the PermissionsKit feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Swift
  • You evaluated both and PermissionsKit fits your workflow better

full PermissionsKit profile →

About OpenCut

OpenCut A free and open source video editor for web, desktop, and mobile. Status OpenCut is being rewritten from the ground up. What's coming: An Editor API First class third party plugins (made possible by a plugin first architecture) Desktop, mobile, and browser from one codebase (Rust core) MCP server (for AI agents) Headless mode (automation, batch rendering) A scripting tab directly in the editor You can still find the previous version at opencut app/opencut classic, which is the one to reach for today. opencut.app still runs the classic version. The rewrite will live at new.opencut.app until it's ready to…

read the full OpenCut overview →

About PermissionsKit

PermissionsKit Universal API for requesting permissions and reading their status — .authorized , .denied & .notDetermined . Each permission ships as a separate product, so the app compiles only the ones it actually uses. Installation In Xcode: File → Add Package Dependencies → paste URL: Then pick the products you need. Add only those — every permission API you link is visible to App Review, and unused ones invite questions about why the app needs them. Permissions Usage Request a permission: Read its status: [!WARNING] FaceID can't tell .authorized from .notDetermined — both come back as .notDetermined . Only…

read the full PermissionsKit overview →

More in Miscellaneous

Related comparisons

More Photo & Video Editors projects

Compare either of these against the rest of the Photo & Video Editors field.

Frequently asked questions

Is OpenCut or PermissionsKit more popular?

OpenCut has 97,156 GitHub stars and PermissionsKit has 5,811. OpenCut has the larger community by that measure.

Are OpenCut and PermissionsKit free?

Both are open source. OpenCut is licensed under MIT and PermissionsKit under MIT. Neither carries a licence fee.

What is the difference between OpenCut and PermissionsKit?

OpenCut is written in TypeScript and PermissionsKit in Swift. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, OpenCut or PermissionsKit?

Choose OpenCut if you want the larger community (97,156 stars) or its MIT licence terms. Choose PermissionsKit if its feature set, stack or MIT licence fits better. Both are self-hostable.