AlbionCore AlbionCore
Sign in

Press K in-game. Your bank's already synced.

A 30 MB read-only desktop app that reads Albion's network traffic on your own machine and pushes a bank snapshot to AlbionCore over TLS. No manual entry, no game-client modification, no Sandbox-side calls.

Read-only · source-available · TLS 1.3 · Authenticode signed

AlbionCore Companion · v0.4.2 Live
Last sync
Triggered by K · 6 s ago
Connected to Albion
Photon stream attached · 0 errors
Bank parsed
1,247 items across 6 cities
Pushed to AlbionCore
TLS 1.3 · 218 ms
Tray-resident · idle 0% CPU TLS 1.3
Size
≈ 30 MB
Tauri / Rust — no Chromium bundled
Idle CPU
< 0.1%
Tray-resident, event-driven
Platform
Windows 10/11
macOS / Linux on the roadmap
Source
MIT, OSS
github.com/ctorres-subeleven/albioncore-companion

How a sync actually flows

Four stages from the moment you open your bank in-game to the row landing in AlbionCore. Every stage runs on your machine; only the final upload leaves it.

01

Attach

Companion attaches to Albion's Photon UDP stream on your machine using Npcap (same capture library Wireshark uses).

02

Press K

Opening your bank or vault triggers Albion to send the item list to your client. Companion observes that response.

03

Parse

Photon packets are decoded into item ids + quantities + city. Nothing touches game memory.

04

Upload

A snapshot is pushed to AlbionCore over TLS 1.3, scoped to your account. Sandbox's servers never see anything.

Built for paranoia

Companion tools have a long history of going sideways. Ours is built so the worst-case is "it doesn't sync" — never "you got banned" or "your credentials leaked."

  • Read-only by design

    Sniffs Albion's network traffic locally via Npcap. Never modifies the game client, never sends anything back to Sandbox's servers.

  • Tauri / Rust

    30 MB installer, no Electron, no Chromium runtime baggage. Tray-resident, idle CPU near zero.

  • Source available

    Every line of the parser, packet handler and uploader is in the public repo. Audit before you trust.

  • Signed installer

    Authenticode-signed via SignPath OSS. Windows SmartScreen accepts it without 'Unknown publisher' warnings.

Is a companion app against the rules?

The companion only reads network data your own client already receives, and never modifies or automates the game — the category of tool the Albion community has long used for market and inventory tracking (the Albion Online Data Project itself works this way). It gives no in-game advantage, no input automation and no hidden information beyond what your client already shows you.

Because it's source-available under MIT, you — or anyone — can verify exactly what it captures and sends before installing it. Authenticode signing via SignPath OSS means Windows SmartScreen accepts the installer without an "Unknown publisher" warning.

The companion never talks to Sandbox Interactive's servers. Every outbound request goes to AlbionCore over TLS 1.3, scoped to your account by a pairing token you generate from the dashboard.

FAQ

Does the companion modify the game?

No. It's strictly read-only: it observes network traffic your client already receives via Npcap, and never writes to the game client or its memory. There's no input automation, no packet injection, no overlays.

What does it send to AlbionCore?

A snapshot of your bank/inventory items and quantities, over HTTPS, when you press K in-game. Nothing is sent to Sandbox's servers. The packet itself is what Albion already sent your client — the companion just decodes and forwards the relevant rows to your AlbionCore account.

Is this against Albion's rules?

AlbionCore's companion only reads network data your own client already receives and never modifies or automates the game — the category of tool the Albion community has long used for market and inventory tracking. It gives no in-game advantage, no input automation and no hidden information.

Which platform does it run on?

Windows 10 and 11 today. macOS and Linux builds are on the roadmap but not shipping yet — packet capture on each platform needs its own permission model (Npcap vs ChmodBPF vs CAP_NET_RAW).

Where do I download it?

Sign in with Discord and the dashboard's /companion page surfaces the signed installer + your pairing code. The installer is gated behind sign-in only so we can scope it to your account; the source is fully public on GitHub.

One keypress, one signed installer

Sign in with Discord to grab the installer and pair your bank. Source on GitHub if you want to read the parser before you run it.