Network Allowlist

Blocked by your corporate proxy? Here is the exact allowlist.

If your secure web gateway will not load this site or will not let Bolt install, this page has everything your network team needs: the specific hostnames, why each one is contacted, and the per-vendor steps to allow them. Written to be forwarded to a security admin without edits.

The allowlist Email [email protected]

The short version

Five hostnames on 443. That is the whole ask.

If you only read one section, allow these outbound over HTTPS and Bolt will install and stay current:

sparcle.app
api.github.com
github.com
release-assets.githubusercontent.com
objects.githubusercontent.com

Everything else on this page is detail: what each host is for, what Bolt contacts once it is running, and how to enter these into your specific gateway.

Bolt does not contact a Sparcle-operated server. There is no activation call, no license phone-home, and no telemetry endpoint. Our own update check points at GitHub, not at us. That is a deliberate architectural choice and you can verify it from the hostnames above: none of them are ours except the site you are reading.

Install time

What the installer contacts.

Required to download and install Bolt. Verified against the shipping installer and a live release-asset redirect.

Hostname

Port

Why it is contacted

sparcle.app

443 / TCP

The download page, the install scripts, and published SHA-256 checksums.

api.github.com

443 / TCP

Resolves which release version is current. One GET, no authentication.

github.com

443 / TCP

Release download URLs. Issues a redirect to the asset host below.

release-assets.githubusercontent.com

443 / TCP

Where the installer bytes actually come from. GitHub redirects here, so allowing github.com alone is not sufficient.

objects.githubusercontent.com

443 / TCP

Legacy GitHub release-asset host. Still serves some older releases; allow it if you pin an older version.

The common failure is allowing github.com but not release-assets.githubusercontent.com. GitHub issues a redirect to that host for the actual bytes, so the download begins and then fails partway. If your gateway logs show a 302 followed by a block, that is this.

Runtime, required

What Bolt contacts once installed.

Two hosts, both GitHub, both only for updates. Block them and Bolt keeps working.

Hostname

Purpose

Detail

github.com

Update check

The desktop updater fetches a small JSON manifest from our GitHub release channel. It does not contact any Sparcle-operated server. Block this and Bolt keeps working; it simply stops offering updates.

release-assets.githubusercontent.com

Update download

The update package itself, if a user accepts an update.

Runtime, optional

Contacted only if you turn the feature on.

None of these are reached by default. Each corresponds to a capability a user or admin explicitly enables, and most of them are your own systems rather than ours.

Destination

Triggered by

Detail

huggingface.co, us.aws.cdn.hf.co, cdn-lfs.huggingface.co

On-device model download, one time per model

Only if a user enables local visual search, local embeddings, or local speech-to-text. These pull open models once and then run entirely on-device. If your policy is to preload models rather than let endpoints fetch them, tell us and we will document the offline path.

Your LLM endpoint

Model inference

Bolt ships no model and has no default cloud endpoint. This is whatever you configure: an on-prem server, an in-tenant cloud model, or a vendor API. If you point Bolt at an internal endpoint, nothing leaves your network for inference at all.

accounts.google.com, www.googleapis.com, gmail.googleapis.com, calendar.google.com

Google Workspace

Only for accounts a user explicitly connects. OAuth is user-consented and revocable.

login.microsoftonline.com, graph.microsoft.com, outlook.office.com

Microsoft 365

Only for accounts a user explicitly connects.

Your MCP server hostnames

Tool and data connectors

Only the MCP servers you configure. Bolt enables none by default.

Bolt's launcher recognition, local search, and utility calls are deterministic and run on-device with no network egress in any configuration. See where the model runs for the full egress picture, including the PII masking that runs before any outbound model call.

Per-vendor steps

How to enter this into your gateway.

The mechanism differs by vendor but the shape does not: a customer-defined allow entry, evaluated ahead of category-based block rules.

Palo Alto Networks (PAN-OS, Prisma Access)

PAN-DB already rates sparcle.app as Computer-and-Internet-Info at Low-Risk, so a URL category rule should not be blocking us. If a PAN gateway is still blocking, look at file-type or download controls on the installer rather than the URL category. To allow explicitly anyway, create a custom URL Category holding the hostnames above and reference it in a URL Filtering profile with the action set to allow, ordered above your block rules.

Zscaler (ZIA)

Add the hostnames as a URL Filtering policy exception, or place them in a custom URL category with an allow rule ordered above your block rules. If your tenant blocks Newly Registered and Observed Domains, note that sparcle.app was registered on 1 December 2025 and is well outside the 30-day NROD window, so that rule is not what is stopping you.

Cisco Umbrella and Secure Access

Add the hostnames to a Destination List with the Allow action and attach it to the relevant policy. Umbrella evaluates allow lists before content categories, so this survives a category-level block.

Netskope

Add the hostnames to a custom URL list and reference it in a Real-time Protection policy with the Allow action, ordered above any category-based block. There is no public self-serve categorization portal, so an allow list is the direct path.

Fortinet FortiGate

Add the hostnames to a Web Rating Override, or create a URL Filter entry with the Exempt or Allow action in the web filter profile applied to the outbound policy.

Broadcom, Symantec, Forcepoint, iboss, Menlo and others

The pattern is the same everywhere: a customer-defined allow list or URL exception evaluated ahead of category rules. If you tell us which gateway you run and what the block page said, we will write the exact steps for it and add them to this page.

Third-party categorization

How the reputation databases currently rate us.

Checked directly at each vendor's public lookup tool on the date shown. We publish the unflattering rows too, because your gateway is going to tell you anyway.

Vendor

You can also ask your vendor to categorize us.

An allow list fixes your organization. Categorization fixes it for everyone, and a submission from a paying customer carries considerably more weight with a vendor than one from the site owner. If you are willing, the submission portals are:

Cisco Talos, Reputation Center, via Submit Content Categorization Ticket
Trellix and McAfee, Customer URL Ticketing, which allows up to three suggested categories
Zscaler, Site Review
Broadcom and Symantec, WebPulse Site Review
Fortinet, rating submission
Palo Alto Networks, Test A Site, already correct as of the table above, so nothing to file

The accurate categories for this domain are Business, Computers and Internet, Software Updates, or Freeware and Shareware. Palo Alto independently arrived at Computer-and-Internet-Info, which is the same answer. sparcle.app is a vendor marketing and download site: it hosts no model, accepts no prompts, and returns no generated output, so the generative-AI categories do not apply to it under the definitions those vendors publish.

Honest framing

Why you are probably seeing this block.

We are a new domain, so some databases have not categorized us yet

sparcle.app was registered in December 2025. Reputation databases rank on crawl history and traffic volume, and a young vendor domain that has not been widely crawled can sit uncategorized for a while. Some gateways block uncategorized destinations by policy. That is a reputation gap rather than a security finding: no vendor we have checked lists this domain as malicious, and Palo Alto already rates it Low-Risk. An allow list is the correct fix while the remaining databases catch up.

Our installers are not yet code-signed

The macOS and Windows binaries are not currently signed with a Developer ID or an OV code-signing certificate, so Gatekeeper and SmartScreen will warn on first launch. We publish SHA-256 checksums so you can verify integrity yourself in the meantime. Signing is funded and in progress, and we would rather say this plainly here than have your endpoint team discover it during a pilot.

We would rather you allow-list us narrowly than broadly

Nothing on this page asks for a wildcard. Every entry is a specific hostname on 443. If a broad rule is the only thing your tooling supports, allow sparcle.app and the GitHub hosts only, and leave the optional runtime entries blocked until a user actually needs the feature.

Verify before you trust

Check the download yourself.

Every release publishes SHA-256 checksums. To verify a download before running it:

# macOS and Linux
shasum -a 256 <the downloaded file>

# Windows PowerShell
Get-FileHash -Algorithm SHA256 <the downloaded file>

Compare the result against the checksum published with the release. If your policy is to review installer scripts before execution, both are plain text and readable in a browser at /install.sh and /install.ps1. If your policy prohibits piped shell installers outright, download the platform installer directly from the download page and skip the script entirely.

Still blocked, or need this in a different format?

We will write the exact steps for your gateway, or answer a security questionnaire, usually within one business day.

Email [email protected] Back to Trust Center