[Release] Canopus 1.0 — free desktop companion for Windows, macOS & Linux: 3D map, fitting with dogma engine, intel & overlay, streaming widgets

[Alexandr_Gercog]

Hi all,

Canopus is a free, open-source (MIT) desktop companion for EVE Online on Windows, macOS and Linux. One app instead of a dozen browser tabs: fitting, intel, a 3D map, route safety, market, industry, your whole character and your corporation.

New in 1.0

• Login in your own browser — the EVE SSO page opens in your default browser, where you can check login.eveonline.com and its certificate; Canopus never sees the page or your password.
• Streaming widgets for OBS: ship, system (optionally delayed against stream sniping), session ISK and kills, killfeed.
• Military Campaigns with objectives, rewards and your contribution.
• Freelance Jobs board with filters the game doesn’t have and alerts for new jobs.
• Sovereignty, raidable Skyhooks and sov timers on the 3D map.
• Capacitor simulated activation by activation, like the game.

3D galaxy map

New Eden at the real SDE coordinates: kills in the last hour, routes drawn on the map, alliance jump bridges with their distance from the capital (Cradle of War), avoided systems and notes, capital jump range, intel reports and sovereignty.

Fitting tool with its own dogma engine

• Built on CCP’s SDE: skills, hull and role bonuses, subsystems, module states, charges, drones, implants, stacking penalties.
• Hover a module to preview every stat; DPS / volley, EHP per layer, capacitor, navigation, targeting.
• All skills V or your character’s skills, with what to train; fit cost in Jita; popular fits from zKillboard; EFT import / export; save straight to your in-game fittings.
• Combat simulator: your fit against any opponent with applied DPS, tracking and range on an interactive map.
• Doctrines: paste a fleet’s fits — who of your characters can fly them, training time, Multibuy list.
• Show Info for everything, with the game’s icons and a readable Effects tab.

Intel

• Local scan: Ctrl+A, Ctrl+C in Local (Cmd on Mac) — every pilot checked for corp / alliance, age, kills and losses, danger and usual ships; alerts when someone dangerous jumps in.
• Intel channels: systems and ships in every report with the jumps from you.
• D-scan and fleet analysis.
• Overlay on top of the game (windowed / borderless), with click-through.
• Alerts in Discord through a webhook.

And more

• Travel: route safety with gate camps, jump planner with fatigue, wormhole lookup, Thera / Turnur.
• Activities: signatures memory, ratting and abyss logs, mining ledger, Military Campaigns, Freelance Jobs.
• Market and industry: five trade hubs, arbitrage between hubs, appraisal, LP store, manufacturing calculator, PI timers.
• Character: all your characters on one screen, skill planner with the best remap (or two along a long plan), blueprint library, assets, wallet, mail, fleet management.
• Corporation (opt-in): structures with fuel and state, alerts for attacks and low fuel, moon extractions and mining.
• English and Russian interface.

Fair play

Canopus only uses official and player-visible data: ESI, the SDE, the chat and game logs the client writes to your Documents folder, and what you copy to the clipboard yourself. It never reads client memory or the screen and never automates input — the same approach as Pyfa or RIFT. Login is standard EVE SSO with PKCE in your own browser; tokens stay encrypted on your computer.

Download

Windows 10/11 · macOS 12+ (signed and notarized by Apple) · Linux (AppImage, .deb). Canopus updates itself.

Release Canopus 1.0 — streaming, campaigns, freelance, login in your browser · GERCOG1390/canopus-desktop · GitHub

Questions, ideas and bug reports: GitHub Discussions and Issues, or right from the app (Settings → Help and feedback). Feedback here is very welcome too. Fly safe o7

[Alexandr_Gercog]

Intel

• Local scan: Ctrl+A, Ctrl+C in Local (Cmd on Mac) and every pilot is checked for corp / alliance, age, kills and losses, danger ratio and usual ships. New arrivals are highlighted, and you get an alert when someone dangerous jumps in
• Intel channels: follows your alliance intel chat logs, recognises systems (including shorthand like “1DQ”) and ships, and shows how many jumps away each report is. “clr” / “nv” count as all clear
• D-scan and fleet window analysis: interdictors, bombers, recons, logi, capitals

Overlay

All of this without alt-tabbing: a small always-on-top window that sits over the game in windowed or borderless mode (on Mac, over a full-screen EVE too).

• The current system, a threat meter and the pilots in Local, with dangerous ones on top
• New arrivals and intel reports within your range appear the moment they happen
• Click-through mode: the overlay stays visible, but clicks go to the game underneath
• Resize and place it anywhere; position, size and opacity are remembered
• Ctrl+Shift+L show / hide, Ctrl+Shift+K click-through on / off (Cmd on Mac), or from the tray menu

[Alexandr_Gercog]

[Officer_Bounty]

First, I want to say I really like Canopus. It’s an impressive piece of software, and I appreciate the work that’s gone into it.

I’ve been checking its network activity before linking my EVE account. The traffic I’ve seen during the login flow appears consistent with EVE SSO, and the authorization URL in Canopus’s log points to login.eveonline.com. That’s reassuring.

My remaining concern is that the EVE login opens in a window inside Canopus, with no visible address bar or certificate information. Since Canopus controls that window, I can’t independently verify the login page in the way I can in my normal browser. The network capture helps confirm the destination, but it can’t show me the certificate or prove what the embedded window could inspect.

Would you consider opening the EVE SSO authorization flow in the user’s default browser instead, then returning to Canopus through the registered callback? That would let users verify they’re signing in to CCP while preserving the normal OAuth/PKCE flow. I’d feel much more comfortable linking my character that way, and I suspect other security-conscious users would too.

This isn’t meant as an accusation—the checks I’ve done haven’t shown me evidence of malicious behavior. I’m raising it because I like the software and want to feel confident connecting my account. Thanks again for building it.

[Alexandr_Gercog]

Thanks a lot for the kind words and for checking the traffic before linking your account — that’s exactly the right thing to do, and the concern was fair.

You were right: an embedded login window is the weaker option, because the app controls it and you can’t verify the page the way you can in your own browser. The recommended practice for desktop apps (RFC 8252) is to use the system browser, and Canopus 1.0, released today, does exactly that:

• The EVE SSO page opens in your default browser, where you can check the login.eveonline.com address and its certificate. Canopus has no access to that page or your password.
• After you log in, the browser hands the result back to Canopus through the registered eveauthcanopus:// link. The OAuth flow with PKCE and the state check is unchanged, and there’s still no client secret and no local port.
• The in-app window remains only as an explicit fallback button for the rare machines where the browser can’t pass the link back.

The login code is public if you want to look: src/main/auth.ts in the repository.

Also new in 1.0:

• Streaming — widgets for OBS (Browser source): your ship, the current system (optionally 2–60 minutes late, against stream sniping), the session’s ISK and kills / losses, and a killfeed from zKillboard.
• Military Campaigns — every faction campaign with its progress, the objectives with ISK / LP / standing rewards, and your own contribution.
• Freelance Jobs board — every public job with reward per unit, pool left and jumps from you; filters the game doesn’t have (hide any number of corporations, minimum reward, within N jumps), alerts for new matching jobs (also to Discord); your jobs and your corporation’s projects.
• Sovereignty on the 3D map — systems coloured by the holding alliance, raidable Skyhooks and sovereignty timers.
• Capacitor is now simulated activation by activation like the game, so “lasts” times match the in-game fitting window.
• Help and feedback right in the app (Settings or Ctrl+K): questions go to GitHub Discussions, bug reports to Issues with the version and platform filled in.

After updating, Canopus asks each character to log in once more (the new features need a couple of extra permissions) and rebuilds its local SDE data, which takes a couple of minutes. Existing installs update themselves; new downloads (Windows, macOS, Linux) are here:

Release Canopus 1.0 — streaming, campaigns, freelance, login in your browser...

Thanks again — this kind of feedback makes Canopus better for everyone. Fly safe o7

[Officer_Bounty]

Thank you for adding browser-based SSO and for responding so quickly. I have a feature request for the combat simulator.

Feature request: time-based PvP scenarios

The combat simulator is a useful start for comparing fits and seeing how damage application changes with range. Could it eventually support time-based engagements, where ship movement, module effects, and pilot choices change the fight as it unfolds?

The current controls let us set distance, speed, and heading, but those describe a single geometry. I’d like to define what each pilot is trying to do and see how range, transversal, damage, and ship state change over time.

Scenario inputs

• Starting range, speed, heading, and propulsion state for each ship.

• A movement choice for each pilot, such as approach, orbit at a chosen range, keep at range, or burn away.

• Optional pilot decisions triggered by range or time—for example, changing ammo, overheating a module, switching movement commands, or trying to disengage.

• A way to compare multiple plausible choices for either pilot, rather than assuming there is only one correct tactic.

Combat mechanics

The highest-priority additions for PvP engagements would be:

• Scrams and disruptors, including tackle ranges and a scram shutting off an active MWD.

• Webs, including their effect on speed and the effect of overheating.

• MWD and AB speed and signature effects, including acceleration and changing velocity.

• Module cycles, capacitor use, and heat damage or burnout.

• Ammo changes and reload time.

• Drone travel time, damage application, and what happens when drones are recalled, destroyed, or told to switch targets.

Later, it would be useful to add other EWAR effects such as neuts, target painters, tracking disruptors, sensor dampeners, and ECM.

A timeline or chart showing range, speed, angular velocity, signature radius, active tackle, capacitor, heat, and shield/armor/hull over the fight would make results easier to evaluate. Please show when and why damage application changes, and make the scenario assumptions visible so users can distinguish modeled mechanics from pilot choices.

I understand a full fight simulator is a large project. Even a first stage that adds movement over time, MWD/AB, scrams, webs, heat, and ammo changes—with remaining mechanics clearly marked as unsupported—would make it much more useful.