AllAddin

IT Policy & Network Egress

Last updated: 4 May 2026 - Version 0.1 - Operated by MeliUX Ltd. For the broader trust posture see /trust.

For IT teams. A BIM developer at your firm wants to install AllAddin and you need to decide whether to allow it. This page answers the questions a vendor-risk-assessment usually asks: what AllAddin contacts on the network, on what ports, and what you can put in a firewall allow-list. Full security and privacy posture lives at /trust; the vulnerability disclosure policy at /security.

1. Network egress endpoints

AllAddin connects outbound only. There are no inbound listeners on the user's machine, no peer-to-peer traffic, and no auto-discovery. All traffic is HTTPS over TCP/443.

Endpoint Protocol / port Purpose
revitclaw-production.up.railway.app HTTPS / 443 Backend API. AllAddin sends the request envelope (intent + structured context, no model contents -- see /trust section 1) and receives generated code + execution outcome.
alladdin.dev HTTPS / 443 Marketing + docs site, version-check endpoint, signed installer download. Hit on first launch and once per day for update polling.
www.gstatic.com
fonts.gstatic.com		 HTTPS / 443 System fonts the panel uses if the local font cache is missing. Optional -- works without if blocked.
ingest.de.sentry.io HTTPS / 443 Crash reporting (Sentry, EU/Germany ingest). send_default_pii=False, user identity is stripped and report text is sanitised before sending; only sanitised stack traces + request metadata leave. When AllAddin crashes it sends this sanitised report so we can fix what broke -- that's how we do support. No identity attached, EU-hosted, no in-app toggle; block this host at the firewall if your policy requires it, with no loss of functionality.
<account>.eu.r2.cloudflarestorage.com HTTPS / 443 Cloudflare R2 (EU-jurisdiction bucket). Direct client upload/download of client-side-encrypted share-link blobs. The client uploads and downloads ciphertext directly over HTTPS; only hit when a user creates or opens a share link.

What AllAddin does NOT contact: third-party AI providers directly (Anthropic / Mistral). All AI calls route through the AllAddin backend; the user's machine never establishes a direct connection to a third-party model provider. That's a deliberate architecture choice -- keeps the API keys out of every user's machine, keeps the audit log centralized, keeps your firm's network exposure to a single allow-listed host.

Processing regions: US (hosting, Anthropic), EU (Mistral, Sentry, Cloudflare R2 (EU share-link storage)), under SCCs / UK IDTA. MeliUX Ltd is UK-registered. See the live sub-processor register.

2. Inbound network surface

None. AllAddin opens no listening ports, runs no services, and does not register itself as a firewall exception. The only inbound connection is whatever Revit itself opens (typically the BIM 360 / ACC / cloud-collaboration sockets that Autodesk's own add-ins use); AllAddin doesn't add to that surface.

3. Telemetry posture

4. Authentication

AllAddin uses a per-user bearer token (we call it an "RC token") issued by us at onboarding. The token lives in %APPDATA%\AllAddin\alladd.ini, encrypted with Windows DPAPI in the user-scope. A stolen alladd.ini on a different machine is useless -- DPAPI can only decrypt on the original Windows account.

Tokens are revocable from our admin panel within seconds. If your firm's security review needs a "we can revoke at any time" guarantee in writing, email trust@alladdin.dev and we'll confirm in the response.

5. Allow-list memo template

Drop-in copy your BIM developer can hand to your IT team to request approval. Edit the bracketed fields and forward.

Internal memo template

To: [IT manager / vendor-risk lead]
From: [BIM developer name]
Re: Approval request -- AllAddin (Revit add-in by MeliUX Ltd)

I'd like to install AllAddin, an AI-assisted Revit add-in, on my machine to [specific use case -- e.g. "automate the sheet-creation workflow on the [Project] project"]. Below is the network-egress profile our IT team needs for an allow-list decision.

Vendor: MeliUX Ltd (UK), Companies House 12413967, ICO registration ZC137214.
Trust posture: ISO 27001 ISMS drafted (51 v0.1 docs, all 93 Annex A controls in scope), full posture at https://alladdin.dev/trust.
Security disclosure: https://alladdin.dev/security.

Network egress to allow-list (HTTPS / 443 outbound only):

No inbound listeners. No P2P. No direct connections to AI providers (Anthropic / Mistral) -- all AI calls route through the AllAddin backend, so your firm's network sees a single allow-listed host, not the broader AI ecosystem.

What AllAddin sends: my natural-language request, the Revit version and active view name, and a small structured summary of the active selection (category and family/type names with counts -- no geometry). Identifying fields (file path, document title, worksharing username, project name/number) are redacted by default before sending; IT can manage this via [privacy] in alladd.ini. What stays on my machine: model contents, geometry, parameter values, the .rvt / .rfa files themselves. Full data-flow disclosure at https://alladdin.dev/trust.

Authentication: per-user bearer token, encrypted at rest with Windows DPAPI (user-scope; stolen file on another machine is useless). MeliUX can revoke any token within seconds.

Installer: signed MSI (Authenticode, publisher "MeliUX Ltd"). Standard Programs-and-Features uninstall -- see uninstall guarantee at https://alladdin.dev/trust.

If a security questionnaire is required, MeliUX maintains a template they'll return filled in: email trust@alladdin.dev.

6. What MeliUX provides on request

Email trust@alladdin.dev for any of the below; turnaround under two business days.