Latest Release

Organizations with roles and site scoping, fleet-wide pool presets, and hardware support for Avalon, Braiins, and Auradine — Pulse becomes a platform for the entire team.

The initial releases of Pulse focused on helping a single operator handle a massive fleet: full visibility in a single pane of glass, bulk actions, and automation of repetitive tasks. But an industrial mining farm is rarely run by just one person. It involves business owners, operations managers, on-site field technicians, and often hosting clients who need visibility into their machines. Alpha4 is the release that transforms Pulse into a workspace for the whole team.

Personal or Business: Tailored to Your Scale

On your first login, Pulse asks how you operate. Personal — for individual farm owners who manage everything themselves. Business — for companies where operations are run by a team.

Until the stable version release, both plans are free and operate without restrictions — your choice should reflect your team structure, not pricing.

This decision is not final: switching between plans is supported in both directions. When returning from Business to Personal, Pulse never deletes data silently — the owner selects a single site that will remain with all its data, and clearly reviews what will be removed before confirming.

Navigation is now split into two tiers: Account — personal profile settings, and Organization — company management. Existing accounts have been migrated automatically with no manual reconfiguration needed.

Team in a Single Workspace

Business plans introduce the Members section. Invitations are sent via email, team members are visible in a centralized list, and access can be paused (blocked) or permanently removed. Members receive notifications when their access status changes — ensuring no one discovers revoked permissions unexpectedly.

Previously, shared farm access often meant sharing a single master credential across multiple operators. This approach was insecure and untraceable: determining accountability was impossible, and revoking one operator's access required changing passwords for the entire team. Now each member operates under their own dedicated account within the organization.

Five Roles Built for Real Operational Duties

Roles in Pulse mirror the actual division of responsibilities on industrial mining sites:

• Owner and Administrator manage everything — from infrastructure to team membership.
• Operations Manager handles daily hardware operations and configuration.
• Technician works on-site but lacks access to critical parameters like pools — preventing accidental changes that could misdirect hashpower.
• Viewer has read-only access — ideal for hosting clients, investors, and auditors.

Roles are selected directly in the invitation modal, ensuring new members receive the exact required permission scope upon their first login.

Site-Level Scoping: Every Member Sees Their Scope

The other half of the access model is physical site scoping. Members can be restricted to specific sites, ensuring they only see assigned devices, metrics, and event logs. Technicians on one site are never distracted by issues on another, and hosting clients only see their own equipment.

Owners and Administrators retain access to all sites, including any created in the future — eliminating the need to manually grant access to leadership when commissioning new facilities. Site assignments are configured alongside roles in the invitation dialog.

Pool Presets: Unified Configuration Across the Entire Fleet

Switching pools across thousands of machines is a frequent yet critical operation: a single typo in a stratum URL or worker name can divert substantial hashpower. Now, pool configurations — URL, Worker, and Password across all three slots — can be saved as named presets.

Presets can be applied within Pools config to an individual miner or a bulk selection. Presets belong to the organization and are accessible across all sites: configure once, and the entire team applies validated stratum configurations without manual data entry.

Autoswitch per Model in Exact Mode

In Performance config under Exact mode, Autoswitch is now configured independently for each hardware model. In heterogeneous fleets, different hardware generations require different operational profiles.

When a model is switched to manual overclocking/tuning (Preset = Disabled), Autoswitch for that model is automatically disabled and locked — preventing conflicting configurations and eliminating manual toggling steps.

Avalon, Braiins, and Auradine

Canaan Avalon miners are now integrated into monitoring alongside existing equipment. Reboot, Change pools, and Find Miner (Locate) work natively just like for HashCore Firmware, Bitmain, and WhatsMiner — without accessing each miner's web interface separately.

Initial support has also been introduced for Braiins OS and Auradine hardware. As Pulse expands manufacturer coverage, operators manage more of their mixed fleet from a single, unified interface.

System Reliability: Automated Recovery

If the service experiences temporary downtime, Pulse renders a status page instead of generic connection errors. Pulse automatically polls for backend recovery and restores active sessions without requiring manual page refreshes.

Summary

Alpha4 elevates Pulse from an individual operator's tool to a collaborative enterprise workspace: every team member has their own account, dedicated role, and site boundaries, while shared configurations like pool presets unify the entire organization.

Pulse remains in alpha — built in close collaboration with the mining operators who rely on it daily. Upcoming roadmap items include: HashCore Firmware with embedded Pulse Agent, device grouping, email and Telegram alerting, an issue tracker, and reporting modules.

Get started, invite your team, and share your feedback — operator input directly shapes upcoming releases.

Registration: https://hashcore.com/pulse