FS Perpetual license · One-time payment

Your front end or an AI agent needs to call, over HTTP, the logic you already have in Visual FoxPro.

REST API from VFP. No IIS. No Apache.

Publish your Visual FoxPro application's logic over HTTP: REST routes, JWT, webhooks and middleware, all declared in plain VFP. And the same function is published as a JSON-RPC 2.0 method and an MCP tool too, so your front end and an AI agent call it the same way.

Who it is for

Your own front end
AI agents, over JSON-RPC and MCP
Incoming and outgoing webhooks
A Windows service in production

Buy license Try free for 30 days View documentation

No credit card. Verify your email and you get 30 days of a full license (not a cut-down build) for FoxServer, FoxCore, FoxBridge, FoxAgent, FoxCli and FoxCli MCP, installer included, in your portal. One per person and product; after 30 days it expires.

This page is served by FoxServer

Not a screenshot, not a diagram. The site you are reading, its API and the endpoint below are served by one and the same process: a Visual FoxPro 9 MTDLL listening for HTTP on a VPS. Do not take my word for it: run it yourself.

Asking the portal for its version with curl

curl -i https://irwinrodriguez.dev/api/paddle/version

FoxServer's response: headers and JSON

HTTP/1.1 200 OK
Content-Length: 100
Content-Type: application/json
Server: Microsoft-HTTPAPI/2.0

{
  "status": "ok",
  "data": {
    "version": "2026-05-24-p2-paddle",
    "build": "24-may-2026 00:00"
  },
  "message": "ok"
}

The "Server" header is http.sys, the HTTP stack built into Windows itself, which is where FoxServer listens: that is why no product name appears there. The FoxPro part is the body: that JSON is returned by a PROCEDURE in a .prg, this portal’s diagnostic endpoint. The Date header was trimmed, and the version and build values change with every deployment.

Features

Standalone HTTP server

A host of its own in .NET/X# that loads YOUR VFP MTDLL over COM and answers the requests. No IIS, no Apache and no web server to configure.

Built-in JWT

Authentication middleware with JWT tokens. Public and private endpoints declared in a HELP comment.

REST, JSON-RPC and MCP

The HELP's "as capability" alias turns a route into a JSON-RPC 2.0 method and an MCP tool. One function, three ways to call it.

Declarative routing

Routes are declared as HELP comments in each VFP method. No additional configuration files.

CORS, HTTPS and webhooks

CORS with configurable origins, HTTPS with a PFX certificate, and incoming and outgoing webhooks with Standard Webhooks signing.

Windows Service

Runs as a Windows service with automatic startup, with no user session open. And it generates its own /openapi.json and Swagger at /docs.

How it works

1

Define a VFP controller

Create a VFP class inheriting from ApiController. Each public method with a HELP comment becomes a REST endpoint.
2

Compile and configure

Compile with FoxForge from the VFP IDE, or with "foxserver build". Port, CORS and JWT live in the server manifest.
3

Start the server

Start FoxServer pointing at your project, or deploy it into the installation so the Windows service serves it.

Pricing

Development seats: Developer licenses, which only accept requests from 127.0.0.1. One-time payment, and the version you buy works forever. To deploy on a server that answers other machines, the Runtime license.

1 Seat

499 €

1 developer

Optional renewal: 125 € a year

Buy

Frequently asked questions

Is the license perpetual?

Yes. You pay once and the version you purchase works forever.

Does it work on Linux or macOS?

No. FoxServer needs Windows 10 or later and the .NET 10 runtime in its 32-bit variant: the host loads the Visual FoxPro COM, which is Windows and 32-bit. The 64-bit one does not work even if it is installed.

Do I need VFP on the production server?

No. Visual FoxPro is not installed on the server: just copy the VFP 9 runtime files (vfp9t.dll, vfp9r.dll, vfp9renu.dll and msvcr71.dll) next to your application's DLL. The server also needs the 32-bit .NET 10 runtime.

Can I deploy it on a customer's server?

Yes, that is what it is for, but with the right license: seats are Developer licenses and only answer 127.0.0.1. Deploying somewhere other machines call needs a Runtime license, sold separately. Mind the direction: FoxServer is not a library that goes inside your EXE, it is a host that loads your MTDLL.

What happens when maintenance expires?

The version you have installed keeps working exactly as before, and the license is perpetual. What you lose is the right to versions published after that date: on download, the portal serves you the latest one you are entitled to.

Ready to modernize your VFP stack?

Download, install and have your first REST endpoint running in under 10 minutes.

Buy now