Licensing

FoxServer is licensed in two different ways, and mixing them up is the product’s most common stumble: seats are Developer licenses, for developing on your own machine, and deploying on a server that answers other machines needs a Runtime license. Both are perpetual and one-time payment.

License types

Seats are Developer licenses: one per programmer. Pick as many as your team needs.

License	Price	Description
Trial	Free	30-day evaluation, all features included.
1 seat	499 EUR	One developer. Personal or freelance use.
4 seats	649 EUR	Up to 4 developers on the same team.
8 seats	799 EUR	Up to 8 developers on the same team.

Buy a license →

A seat is not for deploying Seats are Developer licenses, and the server answers 403 to every request that does not come from 127.0.0.1. Eight seats are still eight development licenses: for a machine on the network or on the internet to call your API you need a Runtime license, which is sold separately. FoxServer Runtime

Perpetual license

The version you buy works forever, and that does not change whatever happens to maintenance. What maintenance bounds is your right to the builds compiled after the date it runs out, and the portal is what enforces it: on download it offers you the latest version you are entitled to, not the latest there is. If no build falls inside your period, the download answers 403 and says why. Renewals are arranged by email, at soporte@irwinrodriguez.dev.

How to install the license

Purchase a license in the customer portal.
Download the foxserver.lic file from your customer portal, on the license detail page. The purchase email tells you it is ready; it does not attach it.
Copy it to config\foxserver.lic inside the folder where you installed FoxServer, which by default is C:\Programas\FoxServer. The server looks for it next to the bin\ it starts from.
Restart FoxServer.

Startup information

On startup, FoxServer prints one line with the license status. What you see there is the kind (Developer or Runtime), which is what decides how the server behaves; the number of seats you bought is not printed:

2026-09-20 09:15:02.114 INFO  FoxServer 0.9.38, console mode
2026-09-20 09:15:02.201 INFO  VFP pool: 2 STA threads, timeout 120 s, queue 16, admission slots 50 (defaults)
2026-09-20 09:15:02.203 INFO  License: Runtime, Tu Empresa, S.L., 1 seat(s), maintenance until 2027-01-15 (active)
2026-09-20 09:15:02.350 INFO  salesapi: docs at GET /openapi.json and GET /docs
2026-09-20 09:15:02.402 INFO  salesapi [api] listening on http://127.0.0.1:8099/

What happens when it expires

Scenario	Behavior
Developer license, request from another machine	403 on all of them. That is what a Developer license does, and it is not a configuration mistake: serving outside localhost needs a Runtime license.
No license file	The host starts and stops at the gate: it serves nothing. Copy the .lic into config\.
The 30-day trial ran out	Buy a license and copy the new .lic into config\. Your code and your configuration do not change.
Maintenance expired	The version you have installed keeps working exactly as before. What you lose is the right to versions published after that date: the portal serves you the latest one you are entitled to, and 403 if there is none.