IR
irwinrodriguez.dev
Back to docs

Licensing

What is licensed

What is licensed is the client, golem-client.exe, on the machine where you use Claude. You buy it per technician (and then the license is tied to their machine) or per team: from 3 technicians to the whole company, with a company license that is not tied to any machine.

The agent on the other machine is free: copy it wherever you need it, it carries no license.

Price and maintenance

TierLicensePriceMaintenance / year
1 technicianBound to the technician's machine249 €69 €
Team 3Company license, not bound to a machine599 €169 €
Team 5Company license, not bound to a machine899 €249 €
Team 10Company license, not bound to a machine1,499 €419 €
CompanyCompany license, not bound to a machine2,490 €690 €

1 technician: the license is tied to the technician's machine and the checkout asks for its ID. From Team 3 up it is a company license: the company is the holder, it is not tied to any machine and the checkout asks for no ID. The number of technicians is contractual: Golem does not phone home or count seats, and Company is unlimited within one company.

One-time payment in every tier. It includes 12 months of maintenance: the builds published during that time.

After that year the license keeps working with the builds inside your maintenance. Renewing it costs what the last column says, per year; it is handled by writing to soporte@irwinrodriguez.dev, there is no self-service on the portal.

Buy a license

Trying it without buying

Without a license, Golem works. It starts in evaluation mode, with the tools that look and a limit of one live connection at a time. The tools that act on the remote machine need a license; they are listed below. If you call one, or try to connect to a second host, it tells you so in those words and tells you where to buy; it is not a fault.

There is no 30-day trial: this is the evaluation, and no sign-up is needed.

These need a license, on the agent:

run_powershell, service (stop, start, restart), start_process, kill_process, kill_job, register_dll, write_file, snapshot, reattach_console, golem_push

And, if the agent publishes FoxAgent, the tools that write or execute in VFP:

foxagent__eval_vfp, foxagent__exec_command, foxagent__execute_tool, foxagent__set_variable, foxagent__set_cursor_field, foxagent__goto_record, foxagent__update_row, foxagent__insert_row, foxagent__set_memo, foxagent__backup_table, foxagent__close_cursors, foxagent__write_source_file, foxagent__reload_procedure, foxagent__build_project, foxagent__run_tests, foxagent__launch_instance, foxagent__close_instance, foxagent__set_role, foxagent__click_control, foxagent__send_key, foxagent__set_control_text, foxagent__set_control_property, foxagent__invoke_method, foxagent__refresh_form

Everything else (host_info, file_info, read_file, tail, list_processes, screenshot, service to query, golem_pull and FoxAgent's queries) works without a license. Scripts in scripts\ and tools from other MCP servers count as tools that act. A licensed client whose maintenance has expired keeps these tools.

Buying: your machine ID

With the 1-technician license, the checkout asks for the technician's machine ID: 16 hexadecimal characters, with or without hyphens. The installer shows it when it finishes and %LOCALAPPDATA%\Golem\golem-client.exe --machine-id prints it. More detail in Installation.

What you will see on startup

golem_status carries a license block with the mode, the holder, the license id, the first eight characters of its fingerprint (that is what support will ask you for, not the file) and the id of this machine.

What you seeWhat it is
License OK — …All in order
Mode evaluationThere is no golem.lic. The tools that look, one connection
"Your Golem trial ended on …"A trial license of the kind issued until September 2026 expired. The client still starts, in evaluation mode
Mode maintenance expiredYour license is good, but this build is newer than your maintenance. Install an earlier build, or renew
LICENSE NOT VALID and it does not startThe file has been tampered with, or belongs to another machine. The message says both ids. A team license is not tied to any machine and never gives this error because of the ID

What travels in golem_status, in the license header and in the log is the mode identifier, which is always evaluacion, licenciado or mantenimiento-caducado and is not translated: it is the word support searches a log for.

Changing machine

This only concerns the 1-technician license; team licenses are not tied to any machine and work on any of them. The ID changes if you reinstall Windows or rename the machine; changing disk, RAM or network card does not change it. If you have to move the license, write to soporte@irwinrodriguez.dev with the new id and it gets reissued.

And does the agent check the license?

No. The agent writes in its golem-audit.log which license each client said it connected with (the id, eight characters of its fingerprint and the mode, without the holder's name), but it does not validate it or turn anybody away because of it: an agent able to lock out the technician who comes to fix the server is exactly what we do not want. Getting in takes the token, and that is checked.