Blazam

Blazam is a web interface for assigning routine Active Directory work to nontechnical staff. It is a strong fit for organizations that want tightly scoped delegation without a software fee, provided they can run it on a suitable domain-joined Windows host.

Overview

Blazam handles common directory tasks across users, groups, organizational units, computers, and printers, including account unlocks, password resets, group assignments, and attribute changes. Its practical advantage is the ability to distribute this work without giving every recipient broad administrative access: reusable access levels can be assigned to groups or individuals, with permissions set by action and attribute.

That control depends on a sound directory structure. Blazam requires Active Directory and a domain-joined Windows host; its documentation says a well-defined OU structure is imperative for granular delegation and advises against installing the application on a Domain Controller. Organizations without that infrastructure, or without a coherent OU structure, should look elsewhere or plan for directory cleanup first.

Key features

Delegated directory work

Action-level and attribute-level permissions let administrators tailor access to a role rather than hand out a general-purpose account. This suits teams that need help with routine requests while retaining control of which operations and data each user can reach.

Rules, integrations, and security

Rule-based actions can run in response to events or on schedules. Filters, ordered processing, conditional stops, and expiration settings provide useful controls for shaping those workflows, though setting them up still calls for administrators who understand the directory and the desired rules.

A REST API and webhook notification subscriptions support integration with other systems. API tokens inherit the permissions of the associated Blazam user, and only admins can currently create tokens for existing Blazam users; that keeps API access tied to an account’s existing scope but limits who can provision it. MFA is described through Cisco DUO or Google Authenticator-compatible TOTP. The documentation also describes encryption for passwords at rest and in transit, TLS/SSL connections, and operation under an unprivileged account.

Pricing

Free and Open Source: free. Blazam is completely free of charge and MIT licensed for personal and commercial use, so there is no paid tier to unlock its core delegation and automation capabilities. The trade-off is that organizations take on self-hosting and deployment decisions rather than buying a hosted service. There is no free trial because the product has a free plan.

Platforms

Blazam supports API, Linux, self-hosted, web, and Windows. These labels do not remove its central infrastructure requirement: it needs Active Directory and a domain-joined Windows host. Windows installation can use IIS or a standalone service; Linux installation supports Apache, nginx, or a standalone service. Documented database choices include SQLite, MSSQL Express, MariaDB, MSSQL, and MySQL, with recommended concurrent-user ceilings varying by database. That range offers deployment flexibility, but administrators should match their database choice to expected concurrency.

Who it's for

Blazam is aimed at overworked system administrators and organizations with limited funding that want nontechnical staff to take on tasks otherwise handled by technical teams. It is most suitable where Active Directory is already in place, OU organization is deliberate, and someone can own an on-premises deployment. It is a poor match for organizations seeking a hosted tool or lacking a domain-joined Windows host.

Pros and cons

• Pros: Free, MIT-licensed use for personal and commercial settings avoids per-seat software costs.
• Pros: Reusable access levels with per-action and per-attribute controls allow routine work to be delegated more narrowly than a broad administrator role.
• Pros: Event- and schedule-based rules, API access, and webhook notifications can support repeatable workflows and integrations.
• Cons: Active Directory and a domain-joined Windows host are required, and installation on a Domain Controller is not recommended.
• Cons: Granular delegation depends on a well-defined OU structure, which can make directory preparation a prerequisite.
• Cons: API tokens can only be created by admins for existing Blazam users, constraining token provisioning.

Alternatives

Active Directory Management Software is the broader category to compare if Blazam does not match your deployment or administrative needs.

• ManageEngine ADSelfService Plus is worth considering if you need a freemium option spanning Android, iOS, Linux, macOS, web, and Windows: its free edition has no expiration, supports 50 users and unlimited domains, and includes 10 Endpoint MFA users.
• Softerra Adaxes is an alternative to evaluate if a 30-day full-functionality evaluation with technical support is useful before choosing a paid product.
• LTB Self Service Password is a free, self-hosted password self-service option for teams that can meet its PHP and LDAP connectivity requirements.
• ManageEngine ADAudit Plus has a free edition capped at 25 workstations, making it an option to compare if that limit fits your environment.
• PWM is another free, open-source password self-service application for LDAP directories.
• Specops uReset is a paid alternative with annual subscriptions priced by the number of users in scope.
• ManageEngine ADManager Plus offers a Governance, Risk and Compliance add-on for $495 a year for Professional Edition users.
• INGOS Active Directory Manager is another option, with pricing on request.

Verdict

Choose Blazam if you need to distribute routine Active Directory administration through finely scoped permissions and can support an on-premises deployment. Its strongest case is the combination of flexible delegation and automation at no charge. Look elsewhere if your organization cannot provide a domain-joined Windows host, has no well-structured OU model, or needs a hosted service.