PulseGTO
Getting started
Cloud vs Engine
You can use PulseGTO in two places. Both have the same interface.
| pulsegto.com (cloud) | Desktop Engine | |
|---|---|---|
| Where it runs | Your browser reads the published strategy database. You cannot start solves on the website. | The engines run on your Windows PC. |
| Browse blueprints | Yes (Strategy tab) | Yes, your own and downloaded ones |
| Where re-solves come from | PulseGTO re-solves spots on its own servers and adds them to the published database over time | Your own re-solves, saved into your .pgb |
| Train your own blueprint | No | Yes (Preflop Settings) |
| Recalculate a postflop node | No | Yes, heads-up and three-way |
| Postflop solve from your own ranges (2 or 3 players) | No | Yes (HU mode card) |
| Daily limit | Free: 10 distinct flop, turn or river boards per rolling 24 h. Browse plan: no cap. | None for local work |
Your local files and the published database are separate. A re-solve you save stays in your own .pgb; nothing is synchronised between your files and the website.
Browse and Engine are separate entitlements. An Engine licence on its own keeps the free limit on the website, and the Browse plan on its own does not include the desktop app. Current plans are on the pricing page.
Switching between them in the app
The desktop app has LOCAL and CLOUD buttons in the top bar:
- LOCAL turns the local engine on or off.
- CLOUD opens pulsegto.com/solver to browse published strategies. Your local engine keeps running.
On the website the same button reads Local blueprint and takes you back.
Training or repairing a preflop blueprint and running a postflop solve need the local engine, as do Recalculate Node and Change Node. If the engine is off, the app offers to start it.
Tabs in the current release
The desktop app opens four tabs: Strategy, Preflop Settings, Postflop Settings and Ranges. History, Library, Jobs, Tree, Live Trainer and Hands show a lock and the note "coming in an update". On pulsegto.com only Strategy is open.
What you are buying access to
The browser library serves published results. It does not run a new custom solve on the server when you click through a strategy. The desktop Engine computes on your Windows machine and keeps the files of your own games. Browsing access and the right to download a published blueprint are separate account capabilities.
Local computation also has a resource cost: CPU time, RAM and room for checkpoint files. A web grid opening instantly is not evidence that a custom six-player game computes instantly. The existing large-run benchmark reports its hardware and tree alongside the time.
Trial activation and licence validation use the internet. Do not interpret local solving as a promise of permanent offline activation. For a first trial, test the actual sequence of starting a run, saving, reloading and solving one node, not only browsing the already published library.