HashCore Pulse 1.0.0-alpha4
The first Pulse releases were about helping one person handle a large fleet: see everything in one window, act in bulk, automate the routine. But a large farm is never just one person. It is the owner, managers, on-site technicians, and sometimes hosting clients who need to see their own devices. Alpha4 is the release where Pulse starts working for the whole team.
Personal or Business: a workspace that fits your scale
On first sign-in, Pulse asks how you work. Personal is for your own farm, when you run everything yourself. Business is for a company where a team works with the fleet.
Until the stable release, both plans are free and work without limits — the choice is about how your work is organized, not about price.
The decision is not final: you can switch both ways. When moving from Business back to Personal, Pulse does not silently delete anything — the owner picks one site that keeps all its data and sees exactly what will be removed before confirming.
Navigation is now split into two levels: Account for your personal settings and Organization for managing the company. Existing accounts have been migrated automatically, so there is nothing to set up again.
The whole team in one workspace
Business plans get a new Members section. Invitations are sent by email, all members are visible in one list, and access can be blocked or removed. Members are notified when their status changes — nobody discovers they lost access by accident while trying to sign in.
Until now, shared access to a farm usually meant one shared login for everyone. That is inconvenient and unsafe: there is no way to tell who did what, and no way to revoke one person's access without changing the password for everyone else. Now every member has their own account in the organization.
Five roles for real responsibilities
Roles in Pulse mirror how responsibilities are split on a real farm:
- Owner and Administrator manage everything — from devices to team membership.
- Operations Manager handles day-to-day device operations.
- Technician works on site but has no access to critical settings such as pools — an accidental edit will not send hashrate to someone else's pool.
- Viewer can see but not change anything — a good fit for hosting clients, investors and observers.
The role is chosen right in the invitation dialog, so a new member gets exactly the permissions they need from their very first sign-in.
Per-site access: everyone sees their own
The second half of the access model is sites. A member can be assigned to specific sites and will see only their devices, metrics and events. A technician on one site is not distracted by incidents elsewhere, and a hosting client sees only their own equipment.
Owner and Administrator see all sites, including ones added in the future — there is no need to grant management access to each new site separately. Like the role, sites are chosen in the invitation dialog.
Pool presets: one configuration for the whole fleet
Changing pools across a large fleet is a frequent and risky operation: one typo in an address or worker name, and part of the hashrate goes nowhere. Now a pool configuration — URL, Worker and Password in all three slots — can be saved as a named preset.
The preset is applied in Pools config to a single device or a whole group. Presets are shared across the organization and available on any site: set it up once, and the whole team uses one verified configuration instead of typing it in by hand.
Autoswitch for every model
In Performance config, Exact mode, Autoswitch is now configured separately for each model. On a mixed fleet this matters: behavior that suits one model does not necessarily suit another.
When a model is switched to manual overclocking, Autoswitch is turned off for it automatically — the settings never conflict, and there is no need to remember to disable it by hand.
Avalon, Braiins and Auradine
Canaan Avalon devices are now monitored on par with everything else. Reboot, pool changes and Find Miner work the same way as for HashCore Firmware, Bitmain and WhatsMiner — without opening each device's web interface separately.
Support for Braiins and Auradine devices has also been added. The more manufacturers Pulse covers, the less equipment on a mixed fleet has to be managed separately.
Stability you do not have to watch
If the service is temporarily unavailable, Pulse opens a status page instead of a confusing error. Pulse checks for recovery on its own and brings you back to work without a manual page refresh.
Summary
Alpha4 turns Pulse from a single operator's tool into a team workspace: every member has their own account, role and sites, while shared settings such as pool presets work across the whole organization.
Pulse is in alpha — we are building the platform together with the people who use it. Already in development: new HashCore firmware with a built-in Pulse agent, device grouping, email and Telegram alerts, an issue tracker and reports.
Join, invite your team and send us feedback — it directly shapes what goes into the next release.
Register: https://hashcore.com/pulse
