Discover Docker services
Turn container metadata into live routes and keep configuration beside the services it describes.
In development · Self-hosted
Protect your services. Keep control.
Clearplane routes and protects Docker services from infrastructure you control. One gateway, one management surface, no hosted control plane.
In development
The supported limited-release installer targets one Linux Docker host. Public release packaging is not available yet.
01
Operating principles
Security policy that stays with your infrastructure
Infrastructure should stay yours.
Clearplane brings routing, policy, and visibility together without sending control of your traffic elsewhere.
Apply traffic policy
Put firewall rules, geographic filters, limits, and safe header controls in the request path.
See what passes through
Inspect request activity from the same local management surface used to operate the gateway.
02
Request path
One public entry point
Edge is the only Clearplane service exposed outside.
Host ports 80 and 443 terminate at Edge. Core, UI, and ContainerProxy remain behind it with no published host ports.
01 / InternetPublic trafficHTTP and HTTPS
02 / EdgeOnly public container80 · 443
03 / PrivateServices and control planeInternal · services · egress
01Public routes
HostHTTPS
app.example.com
/ · web traffic
Host + pathHTTPS
api.example.com/v1
/v1 · API traffic
HostHTTPS
admin.example.com
/ · restricted traffic
02Security gateway
clearplane/
Protect both directions.
- 01TLS terminationEncrypted public entry
- 02Access controlAddress and country controls
- 03Rate limitsSlow abuse and ban offenders
- 04Header controlsShape requests and secure responses
Controls active around proxy hop
03Private destinations
Docker serviceReady
web:8080
app.example.com → web
Docker serviceReady
api:5000
api.example.com/v1 → api
Docker serviceReady
admin:3000
admin.example.com → admin
Applications join the services network. Management traffic reaches UI and Core through protected Edge routes on the private internal network.
Explore the full topology
03
Product interface
Local management, direct evidence
Operate the routes you protect.
Clearplane brings service health, request activity, and assigned security policy into one local management surface. This conceptual preview uses current product vocabulary; its layout and data are illustrative.
Management
Interface preview
operator@local
Overview
Dashboard
All systems operational
Routing
12 activeProtected routes
| Route | Destination | Policy | Source | Status |
|---|---|---|---|---|
| app.example.com/ | web:8080 | Baseline | UI-managed | Protected |
| api.example.com/v1 | api:5000 | API limits | Docker label | Protected |
| admin.example.com/ | admin:3000 | Private allowlist | UI-managed | Protected |
Observability
LiveRecent request logs
- GET /admin/usersadmin.example.com · 203.0.113.42403
- POST /v1/authapi.example.com · 198.51.100.18429
- GET /app.example.com · 192.0.2.21200
Deployment
Security stays close to the traffic.
Routes, enforcement decisions, and operational data remain inside the deployment you control.
- TLS
- Active
- GeoIP
- Loaded
- Configuration
- Current
04
Configuration models
Three workflows, one control plane
Choose where configuration lives.
Clearplane makes configuration ownership visible, so UI changes and declarative container configuration can coexist without competing sources of truth.
Operate through the local interface.
Create routes and policies through the UI or REST API. UI-managed resources remain editable and deletable from the management surface.
Source of truthClearplane UI and REST API
Keep configuration beside services.
Declare routes in Compose and let Clearplane discover and reconcile them. Label-managed resources stay visible but read-only in the UI. Edit the container labels instead.
Source of truthDocker Compose proxy and redirect labels
Use both models together.
Manage some resources declaratively and others through the interface. Every discovered or UI-created resource keeps its configuration source and ownership rules.
Source of truthTracked per resource
05
Beta capabilities
The practical layer
The controls a public service needs.
Start with the gateway functions that matter day to day. Keep every decision inside your own deployment.
Automatic TLS
Terminate encrypted traffic at the gateway.
Access control and GeoIP
Control access with address and location policy.
Rate limits and bans
Slow abusive clients and block repeat offenders.
Response cache and compression
Reuse cacheable responses and negotiate Gzip or Brotli for supported content.
Header controls
Shape request, response, and CORS headers centrally.
Request visibility
Review live traffic from the management surface.
06
Technology
Built on .NET
One .NET stack, front to back.
Clearplane uses the modern .NET platform across its gateway, management APIs, proxy pipeline, and local operator interface.
The current runtime and toolchain across the deployment.
Hosts the public gateway and private management APIs.
Provides the reverse-proxy foundation beneath Clearplane policy.
Runs the local management experience in the browser.
Built around Docker
Routes follow your services.
Clearplane watches the environment it runs in and keeps routing close to your containers. Application services join the services network; only Edge accepts public traffic.
Explore the network modelDocker host
service / webdiscovered
clearplaneroute active
service / apidiscovered
In development
The product is taking shape.
The current product covers routing, TLS, discovery, traffic controls, caching, transforms, and operational visibility.
Install on a single Linux Docker host with Docker Compose. Broader production rollout remains in development.
07
Community
Where Clearplane takes shape
Build it with us.
Join operators shaping Clearplane. Share what works, surface what needs attention, and follow development.
Talk directly with the community.
Get development updates, compare deployments, share feedback, and work through product questions.
Join the DiscordFollow the project on GitHub.
Watch the Clearplane organization for project activity and updates as development moves forward.
Follow on GitHubKeep the conversation public.
Follow release notes, longer discussions, and discoveries that should remain easy to find.
Visit r/clearplane