App Store template

DeeplX

Deploy the self-hosted DeeplX translation API on Sealos and connect applications to its HTTP endpoint. This independent gateway integrates with DeepL translation.

Launch in your Sealos workspace.

Source Deploy guide Website

DeeplX template preview — Template previewFull screenshot

Template deployments: 14 on Sealos
Deployment: Your own instance
Category: Tools

About this template

Overview

Deploy the self-hosted DeeplX translation API on Sealos and connect applications to its HTTP endpoint. This independent gateway integrates with DeepL translation.

How to deploy DeeplX

Choose Deploy now to start DeeplX in your Sealos workspace.
Review AUTHKEY in the deployment form.
Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the DeeplX 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.

DeeplX

Overview

DeepL Free API (No TOKEN required)

This Sealos template deploys DeeplX as the deeplx application. It uses the repository-maintained Sealos manifest and keeps deployment, networking, and storage configuration inside the template.

Deploy on Sealos

Open this template in the Sealos App Store, review the configuration values, and click Deploy. Sealos renders the template variables, creates the required Kubernetes resources, and manages the public endpoint for the application.

Access

After deployment, open https://${{ defaults.app_host }}.${{ SEALOS_CLOUD_DOMAIN }}. The concrete hostname is generated from defaults.app_host and your Sealos Cloud domain.

Configuration

The following user-facing inputs are available during deployment:

Name	Description	Required	Default
`AUTHKEY`	DeepL Official AuthKey. If you have set it up, after the 429 response, the official AuthKey will be used for the request. If multiple authKeys are used simultaneously, they need to be separated by commas.	`false`	``

Keep sensitive values in Sealos-managed inputs or generated defaults. Do not commit private credentials to the template repository.

Official Links

Official website: https://github.com/OwO-Network/DeepLX
Source repository: https://github.com/OwO-Network/DeepLX

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.

One-click deployment
Start with a ready-made template. Review its configuration and launch from the Sealos console.
Managed Kubernetes
Run on managed infrastructure with built-in workload scheduling and recovery.
Automatic HTTPS
Give your application a public HTTPS endpoint with certificates managed for you.
Persistent storage
Keep application data on persistent volumes across container restarts.
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.