Request routing
Define incoming listeners and route requests to one or more upstream applications.
FEATURES
Use this page to describe what Refined Engine can do today, what is experimental, and what is planned.
Define incoming listeners and route requests to one or more upstream applications.
Keep host, client, and protocol information available to applications through deliberate forwarding behavior.
Reserve routes for lightweight built-in services instead of requiring another application for every operational endpoint.
Provide simple health behavior for deployment checks and infrastructure monitoring.
Add benchmark results, latency numbers, throughput tests, or comparison notes here.
List supported protocols, operating systems, runtimes, deployment platforms, or integrations.
Explain what is stable, what is in preview, and what you are planning for future releases.
This card is intentionally open-ended so you can replace it with project-specific information.