Deploy and Host Teleproxy on Railway

High-performance Telegram MTProto proxy with Fake-TLS, dynamic record sizing, and strong DPI resistance. A modern self-hosted alternative to the official MTProxy.

Telegrm proxy

About Hosting Teleproxy

Teleproxy is a modern, high-performance implementation of Telegram's MTProto proxy protocol. Unlike the official MTProxy, Teleproxy offers significantly better resistance against Deep Packet Inspection (DPI) through its advanced Fake-TLS implementation, dynamic record sizing, and anti-replay protection.

This Railway template deploys Teleproxy as a lightweight container with sensible defaults. It supports automatic secret generation, Fake-TLS camouflage using a chosen domain, advertisement tags via @MTProxybot, and multiple worker processes for better performance. The container also includes built-in Prometheus metrics for monitoring.

Hosting Teleproxy on Railway allows you to run a private, censorship-resistant Telegram proxy without managing a VPS or dealing with complex server configuration.

Common Use Cases

Self-hosted Telegram proxy with strong anti-DPI capabilities
Private MTProxy for personal or group use in restricted networks
High-performance alternative to the official Telegram MTProxy
Proxy with Fake-TLS to bypass advanced censorship systems
Monetizable proxy using advertisement tag from @MTProxybot

Dependencies for Teleproxy Hosting

This template uses the official Teleproxy Docker image:

ghcr.io/teleproxy/teleproxy:latest

Deployment Dependencies

Railway TCP Proxy enabled on port 443
Persistent volume mounted at /opt/teleproxy/data (recommended)
No database or Redis required

Teleproxy automatically downloads the latest Telegram proxy configuration on startup and refreshes it periodically.

Comparison

Feature	Official MTProxy	Teleproxy	Notes
Fake-TLS (EE Mode)	Basic	Advanced (TLS 1.3 + dynamic sizing)	Teleproxy much stronger
DPI Resistance	Moderate	Excellent	Teleproxy wins
Dynamic Record Sizing	No	Yes	Harder to detect
Anti-Replay Protection	Weak	Strong	Better security
Multiple Secrets	Yes	Yes (up to 16 with limits)	More flexible
Prometheus Metrics	No	Yes	Better monitoring
Docker Image Size	~57 MB	~8 MB	Much lighter
Active Development	No (outdated)	Yes	Actively maintained
Ease of use on Railway	Good	Excellent	Better defaults

EE_DOMAIN Options & Recommendations

EE_DOMAIN is used to enable Fake-TLS mode, making your proxy traffic look like normal HTTPS traffic to the chosen domain. This is one of Teleproxy's strongest features against DPI.

Recommended Domains

Domain	Recommendation	Pros	Cons	Score
`www.microsoft.com`	Highly Recommended	Very stable, widely used, good TLS support	Slightly more monitored in some regions	9/10
`www.cloudflare.com`	Highly Recommended	Excellent TLS, very common, good performance	Can be blocked in some strict networks	9/10
`www.google.com`	Good	Extremely common, fast	Heavily monitored in some countries	8/10
`www.apple.com`	Good	Clean, good reputation	Slightly less common than others	7/10
`www.amazon.com`	Acceptable	Large company, stable	Can be more restricted in some regions	6/10

Recommendation: Use www.microsoft.com or www.cloudflare.com as default.

Note: You can change the EE_DOMAIN value after deployment. The domain must support TLS 1.3.

Why Deploy Teleproxy on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Teleproxy on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.