Start here

Three ways in. One Fortifie account.

Upload a build on the website, call Fortifie from your editor, or use the CLI from your terminal or CI. These are doors into the same product, not separate plans. Start with a free scan. No card needed.

Get a free scan See plans

1 · Website

Upload a file

This is the fastest first run. Sign in with your email, then drop a JavaScript file on the Scan page. Mac apps work too, but may take longer. Fortifie reads what the shipped build gives away and never launches the app. The file is uploaded to Fortifie and deleted after the run. Website uploads are limited to 20 MiB.

  1. Create a free account. We email you a one-time sign-in link. One free scan per account, no card.
  2. Upload the build you own. JavaScript is self-serve. Mac apps run on our Mac build machine, which is not always online, so they may take longer. Android, iOS, .NET, JVM, Windows and native are coming soon. Contact us if you need one now.
  3. Read the scan, then upgrade to harden. Solo and Studio can harden from the same page, or from your editor. Studio includes Leak Finder, which looks for public listings of your app after you ship. On Solo it is a $49/month add-on. You review a drafted notice; Fortifie does not send it.
Upload a build

2 · Editor

Use it from your editor

The hosted Fortifie MCP lets Cursor, Claude, Codex or any MCP client scan and harden a build you own, without leaving the editor. It uses the same Solo or Studio plan as the website. Hosted assess can scan a raw JavaScript file. A Mac app may take longer, and is refused if our Mac build machine is off. The build is uploaded to Fortifie, processed on our side, and deleted after the run. Free accounts cannot issue API keys.

  1. Choose Solo or Studio under Billing (test mode until live checkout is on).
  2. Create an API key on the API keys page. It is shown once.
  3. Point your client at the hosted MCP with the snippet below, then restart the client.

Endpointhttps://fortifie-mcp.fly.dev

Authorization: Bearer YOUR_API_KEY

Tools the server exposes: assess, harden, status, fetch_audit.

Your Keys page repeats this endpoint. Add it in Cursor, Claude, Codex or any client that can call an HTTP MCP or send that bearer header. There is no local FORTIFIE_BIN to install for the hosted path.

3 · CI

CLI and CI

Use the same Fortifie account from your terminal or CI. Install the CLI, sign in (or set an API key), then assess or harden a build you own. Self-serve protection today is JavaScript. Mac apps are supported but may take longer. The build is uploaded, never launched, and deleted after the run.

python3 -m pip install https://fortifie.xyz/cli/fortifie-0.2.1-py3-none-any.whl
fortifie login
fortifie assess fixture://owned-js-sample

Create a key on the API keys page if you would rather set FORTIFIE_API_KEY yourself (Solo or Studio required). Copy-paste GitHub Actions and GitLab CI snippets are on the CLI page. There is no Marketplace action and no PyPI package yet.

CLI install and CI snippets