App Store template
FreeLLMAPI icon

FreeLLMAPI

A personal AI gateway with provider key management, automatic model fallback, an OpenAI-compatible API, and a web dashboard.

Launch in your Sealos workspace.

FreeLLMAPI template preview
Template previewFull screenshot
Template deployments
30 on Sealos
Deployment
Your own instance
Category
AI

About this template

Overview

FreeLLMAPI is a personal AI gateway that manages provider credentials and routes requests through an OpenAI-compatible API. This template deploys the official FreeLLMAPI v0.9.8 image with its web dashboard and persistent SQLite storage on Sealos Cloud.

From the documentation

FreeLLMAPI combines provider key management, model routing, fallback chains, a chat playground, and request analytics. Add your own provider credentials after creating your dashboard account, then connect compatible clients using the gateway's unified API key and /v1 base URL. Provider availability, quotas, and charges follow each provider's terms.

How to deploy FreeLLMAPI

  1. Choose Deploy now to start FreeLLMAPI in your Sealos workspace.
  2. Sign in to Sealos and review the template configuration in your workspace.
  3. Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the FreeLLMAPI template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.

Template configuration and setup

Access after deployment

Use the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.

Hosting and billing

Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.

Compare Sealos resource plans
Read full documentationCollapse documentation

For current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.

Deploy and Host FreeLLMAPI on Sealos

FreeLLMAPI is a personal AI gateway that manages provider credentials and routes requests through an OpenAI-compatible API. This template deploys the official FreeLLMAPI v0.9.8 image with its web dashboard and persistent SQLite storage on Sealos Cloud.

FreeLLMAPI website

About Hosting FreeLLMAPI

FreeLLMAPI combines provider key management, model routing, fallback chains, a chat playground, and request analytics. Add your own provider credentials after creating your dashboard account, then connect compatible clients using the gateway's unified API key and /v1 base URL. Provider availability, quotas, and charges follow each provider's terms.

The official container serves the React dashboard and Express API together on port 3001. Sealos provisions one application replica, a 1 GiB persistent volume, and a public HTTPS address. The SQLite database, saved conversations, provider settings, and encryption key survive Pod restarts on that volume.

This deployment follows FreeLLMAPI's personal, single-user model. The first account claims the dashboard; its password protects dashboard access, and the separate unified API key authenticates inference clients.

Common Use Cases

  • Personal coding assistants: Connect OpenAI-compatible tools to one gateway URL.
  • Provider fallback: Route requests across configured providers and models as availability changes.
  • Model evaluation: Try prompts in the Playground and inspect usage in Analytics.
  • Credential management: Keep provider keys in your own deployment and give clients a unified API key.

Dependencies for FreeLLMAPI Hosting

The template includes Node.js, the built dashboard, the API server, SQLite, and persistent storage. Provider credentials are configured inside FreeLLMAPI after deployment.

Deployment Dependencies
Implementation Details

Architecture Components:

  • Application: One StatefulSet running ghcr.io/tashfeenahmed/freellmapi:v0.9.8, serving the dashboard and API.
  • Initialization: A short initialization container creates and validates the persistent encryption key before the server starts.
  • Storage: One 1 GiB persistent volume mounted at /app/server/data; runtime state lives in its runtime subdirectory.
  • Networking: A Service on port 3001 and Sealos Ingress with automatic HTTPS.

Configuration:

ItemTemplate setting
Application replicas1
Main container limits / requests100m CPU, 128Mi memory / 10m CPU, 12Mi memory
Initialization limits / requests100m CPU, 128Mi memory / 10m CPU, 12Mi memory
Database/app/server/data/runtime/freeapi.db
Encryption key/app/server/data/runtime/.encryption-key, owner-only 0600 permissions
Health endpoint/api/ping
Runtime identityNon-root UID/GID 1000

The encryption key is generated once from operating-system randomness, validated as 64 hexadecimal characters, and loaded as ENCRYPTION_KEY in production mode. Back up the database and its original encryption key together using a protected backup location. Keep one replica for this SQLite deployment and adjust CPU or memory as usage grows.

Private-network provider URLs are blocked with FREEAPI_BLOCK_PRIVATE_PROVIDER_URLS=true. Configure a publicly reachable HTTPS provider endpoint for custom providers.

License Information: FreeLLMAPI is licensed under the MIT License.

Why Deploy FreeLLMAPI on Sealos?

Sealos is built on Kubernetes and provides application management through Canvas, resource cards, and an AI dialog.

  • One-click deployment: Provision the application, persistent storage, and HTTPS endpoint from one template.
  • Resource efficiency: Pay-as-you-go resources start at the tested personal low-load configuration.
  • Persistent state: Keep the account, provider configuration, conversations, and key across restarts.
  • Operational visibility: Inspect logs and resource usage from the application's Canvas resource card.

Deployment Guide

  1. Open the FreeLLMAPI template and click Deploy Now.
  2. Review the deployment and confirm. Account and provider credentials are entered in the application after it starts.
  3. Wait for deployment to finish, typically 2-3 minutes. Sealos opens the Canvas; the application resource card provides logs, settings, and its public HTTPS address.
  4. Open the application address. On Create your account, enter a valid email address and a password of at least 8 characters, then click Create account.
  5. Remote setup reveals a Setup code field. In Canvas, open the FreeLLMAPI resource card and view the main container logs. Find the latest First-run setup code: line, enter that code in the form, and submit again. The code changes when an unclaimed server restarts and is consumed after registration.
  6. Open Keys → Add key and configure your provider. For an OpenAI-compatible custom provider, supply its HTTPS base URL, API key, and supported model IDs.
  7. Open Playground, choose a configured model, and send a short message. The Keys → Unified API key tab provides the credential and base URL for compatible clients.
Sign In and Password Recovery

After registration, use the same email and password on Sign in. Account creation is available only until the first account has been created.

For password recovery, choose Forgot password? → Send reset code. Read the newly generated password reset code in the application's main container logs through Canvas, enter it with a new password of at least 8 characters, then sign in again. Log access is required for both remote first-run setup and password recovery.

Configuration and Scaling

Manage providers, models, routing, and client credentials inside FreeLLMAPI. For infrastructure changes, open Canvas and describe the change in the AI dialog or edit the application resource card. Increase CPU or memory for larger payloads or heavier concurrent use while retaining the single application replica.

Troubleshooting

The setup code is rejected: Read the latest First-run setup code: from the currently running main container. Restarting an unclaimed instance generates a fresh code.

A client receives an authentication error: Use the unified API key from Keys → Unified API key with this gateway. Configure the upstream provider's own key separately in Keys.

A model request fails: Check the provider's key, model ID, quota, and HTTPS base URL. A custom provider's model ID must match one that endpoint serves.

An existing database fails to start after its key was removed: Restore its original .encryption-key alongside the database. The initialization guard requires that original key to preserve access to encrypted provider credentials.

License

This Sealos template is provided under the template repository's license. FreeLLMAPI itself is distributed under the MIT License.

From launch to everyday operations

Why deploy
on Sealos

A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.

  1. One-click deployment

    Start with a ready-made template. Review its configuration and launch from the Sealos console.

  2. Managed Kubernetes

    Run on managed infrastructure with built-in workload scheduling and recovery.

  3. Automatic HTTPS

    Give your application a public HTTPS endpoint with certificates managed for you.

  4. Persistent storage

    Keep application data on persistent volumes across container restarts.

  5. Room to grow

    Adjust CPU, memory, and replicas from the console as your workload changes.

One template. Connected resources.

You Get the Whole Stack

Sealos provisions the resources defined by your template and brings them together in your workspace.

  • App Service

    Container workloads with configurable CPU, memory, and replicas.

  • Public HTTPS URL

    An address for your app, with managed TLS certificates.

  • Database

    A database provisioned alongside your app when the template calls for one.

  • Persistent Volume

    Storage for the files and data your application needs to keep.

  • Environment Variables

    Application settings and secrets configured in one place.

  • Logs & Metrics

    Inspect container logs and resource usage from the console.

Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.

Explore more production-ready templates.

More