> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dcdeploy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# TCP Proxy & Public URLs
> The **TCP Proxy** in DCDeploy allows you to expose workloads that communicate over **raw TCP protocols** (non-HTTP). This is especially useful for **databases, message brokers, and custom TCP-based services**. With **TCP Public URLs**, you can also securely connect to these services from outside DCDeploy.
***
## When to use TCP Proxy?
* **Databases** – Expose PostgreSQL, MySQL, or Mongodb for internal/external access.
* **Message Brokers** – Kafka, RabbitMQ, or custom TCP services.
* **Custom Protocols** – Any app or service that doesn’t use HTTP/HTTPS.
***
### Example: Mongo-db with TCP Proxy
### TCP Public URLs for Databases
When you set protocol: tcp, DCDeploy provisions a public TCP endpoint so you can connect to your database or TCP service from anywhere.
### PostgreSQL Example
Mysql Example
### Best practices
* Secure your database – Never leave databases open without authentication. Always set strong passwords.
* Restrict access – Use firewall rules or allow-list IPs if possible.
* Prefer private networking – For production workloads, use DCDeploy’s private VPC or service-to-service networking instead of exposing databases publicly.
* Use secrets to store credentials rather than hardcoding them in your worhload form.
***