OpenAI-compatible. Self-hosted. Centrally licensed.

MFI AI Gateway

Bring provider accounts behind one controlled endpoint, install on your own Linux server and manage licensing, releases and access without rebuilding your stack.

OpenAI-compatibleOne API shape for clients
Linux installerGuided systemd deployment
Signed releasesMetadata and checksum verification
One active serverSimple installation transfer
One controlled gateway

Built for teams that want ownership without operational clutter

MFI AI Gateway runs on infrastructure you control while centralizing provider connectivity, access policy, release delivery and license state.

MFI AI Gateway customer portal showing license and installation status
Provider control

One endpoint for your AI clients

Keep client configuration stable while provider accounts and routing rules are managed behind the gateway.

Deployment

Install on a clean Linux server

The installer provisions the compiled service, systemd unit and runtime directories with consistent versions.

Release trust

Verify before every install

Signed release metadata, archive size and SHA-256 checks protect the update path from accidental or altered packages.

Licensing

Move without support tickets

Activating a new server transfers the active installation. The previous server loses access on its next license check.

Visibility

See license and service state

The customer portal keeps installation, renewal, download and support information in one practical workspace.

Compatibility

Keep existing OpenAI-style clients

Use familiar request formats and point supported tools at the gateway endpoint instead of each provider separately.

From purchase to running service

A direct setup path

The account, license and installer flow is designed around one product and one 30-day period.

1

Create your account

Use your email and password to open the customer workspace.

2

Open a payment request

A payment reference is reserved for 48 hours while the manual pilot payment is reviewed.

3

Receive the license key

After approval, the key appears once in your customer portal.

4

Run the verified installer

Install the latest signed release and enter the key when prompted.

Designed around clear boundaries

Compiled delivery and server-driven license checks

The customer package contains compiled application artifacts. License decisions, active installation state and release signatures remain controlled by the service infrastructure.

Short-lived sessions

Portal sessions use secure browser cookies and expire automatically.

One-time key delivery

A newly issued license key is exposed once after payment approval.

Public status

Customers can check service availability without exposing internal operations details.

Common questions

Before you install

Does the software run on my own server?

Yes. The commercial package targets a clean x64 Linux server and runs as a systemd service.

What happens when I move to a new server?

Enter the same license key on the replacement server. The new installation becomes active and the previous one stops after its next license check.

When does the 30-day period begin?

The period begins on the first successful activation, not when the key is created.

Can I inspect service availability before purchase?

Yes. The public status and download pages remain available without an account.