Support & trust

FileRise is self-hosted and maintained by an independent developer. This page explains how to get help, how to report security issues, and how licensing works.

Support channels

• GitHub issues: Best for bugs, feature requests, and reproducible errors.
• Email: License questions, billing issues, or private account concerns.
• Discord: Community questions, setup tips, and general discussion.

Email: [email protected]. GitHub: github.com/error311/FileRise. Pro purchasers can request a Discord role by emailing from the checkout email (do not post license keys publicly).

Support expectations

FileRise Pro includes priority help for reasonable setup questions. To speed up support, include:

• FileRise core version and Pro bundle version.
• OS, PHP version, and web server (Nginx/Apache).
• Exact steps to reproduce the issue.
• Relevant logs or screenshots, with secrets removed.

Support is best-effort and may take a few business days depending on volume. Please send sensitive details (license keys, order IDs) by email only.

Security contact

If you discover a security issue, please email [email protected] with details and a proof of concept. Please avoid posting security reports publicly until a fix is available. We will acknowledge reports as quickly as possible.

Security advisories: github.com/error311/FileRise/security/advisories.

Licensing overview

• FileRise core: MIT licensed and free to use.
• FileRise Pro: Paid add-on bundle with signed license keys (FRP1...).
• Local validation: Licenses validate locally with a public key (no phone-home checks).
• No telemetry: FileRise does not ship usage tracking in the core app or Pro bundle.
• Custom-built stack: Purpose-built PHP/JS stack with no mandatory SaaS dependency.
• Optional renewals: Add 12 months of updates if you want continued access to new bundles.

Review the Terms of Service and Privacy Policy for full details.