Replace the UDP server, not the application logic
A conventional request/response service needs long-running processes, listeners, load balancing, patching, and capacity planning before application code receives its first packet. Proxylity turns the packet into a native event and invokes Lambda or Step Functions in your AWS account.
UDP clients → Proxylity managed event source → Lambda or Step Functions in your AWS account → UDP replies
One contract, several implementation choices
Proxylity delivers a batch of packets as structured JSON. Each packet includes a tag that application code can use to return a response. A handler can reply to every packet, one packet, or none. The same contract is demonstrated with Lambda implementations in multiple languages and a code-free Step Functions state machine.
Deploy quickly
The introductory CloudFormation example creates the listener, destination, IAM role, and handler as one stack.
Scale from zero
There is no application server waiting for traffic. Your selected AWS destination runs only when packets arrive.
Batch intentionally
Adjust batch count and timeout to choose the balance between response latency and destination invocation cost.
Go global incrementally
Add region-specific destination ARNs so packets are processed close to where they arrive and avoid unnecessary cross-region dependencies.
Try it under your traffic pattern
The repository includes a basic deployment test and a multi-region tool that sends 100 packets, records response latency, and groups responses by region. That is a functional starting point, not a published benchmark. Deploy the stack, increase the traffic with tooling appropriate to your workload, and observe where your own latency, batching, and destination limits appear.
Deploy the Lambda example →
Deploy the Step Functions example →
Test multi-region routing →