owo-network/dlx

DLX - Self-hosted translation API server. Unofficial; not affiliated with DeepL SE.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 7th, 2026
Created on October 17th, 2022
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 664
Total Stargazers: 8,700 (+0)
Total Subscribers: 47 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.9 hours
Mean response time: 6.9 days
90th percentile: 27.7 days
Tracked items: 55

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 14% of issues opened in the past year have been closed. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

DLX is a self-hosted translation API server written in Go that exposes a simple HTTP API for translation requests.

The project solves the problem of needing a private, self-controlled translation service by wrapping translation functionality behind an HTTP API that runs on port 1188. It can be deployed via Docker using images available on Docker Hub and GHCR, or by running a downloaded binary for your platform. The tool allows developers to integrate translation capabilities into their applications without relying on external API services or managing direct dependencies on proprietary translation providers.

DLX suits projects where translation needs must be handled privately or where developers want to avoid direct API dependencies. It works well for applications that require a simple HTTP interface to translation services and can be self-hosted in containerized or standalone environments. The project explicitly disclaims any affiliation with or endorsement by DeepL SE, and the recent repository rename from DeepLX to DLX reflects this separation following a trademark notice.

The project maintains active development with regular updates to its codebase. The tool is distributed through multiple channels including Docker images and platform-specific binaries, indicating ongoing attention to accessibility and deployment options. Community engagement is supported through a dedicated discussion group for users to share questions and feedback.