Skip to content
    From code to store, for Electron · Free beta

    Ship Electron AppsWithout the Headaches

    Code signing, notarization and store releases for Electron, without building your own CI/CD. Start today with a free Release Readiness Check that finds what blocks your release and how to fix it.

    Run a Free CheckSee the Roadmap

    Free during beta. No credit card required.

    How it works

    From your repo to a signed release in four steps. Connect and Analyze are live in the beta; Build & Sign and Publish are next.

    • Live

      Step 1: Connect

      Link your GitHub repo. We read your config and entry files through the GitHub API. Nothing to install, no workflow files.

    • Live

      Step 2: Analyze

      A Release Readiness report on signing, notarization, security, store requirements and auto-update, with a fix for every issue.

    • Coming soon

      Step 3: Build & Sign

      We build on our infrastructure, sign with your certificates and notarize for macOS. All platforms in parallel.

    • Coming soon

      Step 4: Publish

      Release to the Mac App Store, Microsoft Store or GitHub Releases with auto-update.

    What the check looks at

    The settings that most often break a signed Electron release, checked before you build

    • App Essentials

      package.json fields, main entry, build scripts, and whether electron sits in devDependencies.

    • Build Config

      electron-builder appId, targets, files, asar and icons. Forge projects are detected and flagged.

    • Signing & Notarization Readiness

      Hardened runtime, entitlements and notarization setup for macOS; signing config for Windows.

    • Store Requirements

      Mac App Store sandbox entitlements and Microsoft Store packaging, when you target the stores.

    • Auto-Update Setup

      electron-updater, publish config and the zip target macOS needs for updates.

    • Security Settings

      contextIsolation, nodeIntegration, sandbox, CSP and hardcoded secrets in your source.

    Live · epp CLI

    Run it from your terminal

    The same Release Readiness Check, without leaving your editor. Sign in once with your Electron Publish Pro account, then check any Electron project folder.

    • Reads files from your project folder: any git host, uncommitted changes included
    • epp check --fail-on fail stops a CI pipeline when a release blocker shows up
    • epp check --json gives AI coding agents a report they can act on
    View on npm
    $ epp login
Signed in as you@company.com

$ epp init --goal direct --platforms macos,windows
$ epp check

Release Readiness  68/100

[PASS] Build Tool Configuration
[WARN] Security Configuration
       → Set sandbox: true in webPreferences
[FAIL] macOS Direct Distribution
       → Add an afterSign hook with @electron/notarize
    Example terminal session running epp login, epp init and epp check
    Managed builds · Coming soon

    We handle the infrastructure

    No CI/CD to set up: your app is built, signed and published on our managed infrastructure. Like Expo, but for Electron. This part isn't live yet. Today you get the readiness report shown here; vote for what you need next, and the most-wanted parts get built first.

    • Signed and notarized macOS builds
    • Windows code signing
    • GitHub Releases with working auto-update
    • Alerts when your Electron version goes out of support
    Readiness report
    Example
    Package.json essentials
    Pass
    Build config (appId, targets)
    Pass
    Security settings
    Pass
    macOS hardened runtime
    Warning
    macOS notarization
    Fail
    Windows signing
    Warning
    Auto-update
    Pass
    Readiness score68%
    Example readiness report with passed checks, warnings and a failed notarization check

    Frequently asked questions

    Everything you need to know about Electron Publish Pro