Spend less per message
UDP skips connection setup and ordered-stream bookkeeping. For independent messages, that can mean fewer bytes to transmit, less CPU work, and longer battery life for your devices.
AWS re:Invent 2026 · Let's connect
Bring your UDP devices and services to AWS without managing servers. Update your application without restarting its receiving endpoint, keep fresh messages moving, and spend less moving and processing data.
Bring a question, a sketch, or just your curiosity. You don't need a finished architecture.
See what you can try in the live demoLess friction. More progress.
UDP skips connection setup and ordered-stream bookkeeping. For independent messages, that can mean fewer bytes to transmit, less CPU work, and longer battery life for your devices.
Fresh UDP updates don't wait for an earlier packet to be retransmitted. Avoid TCP's head-of-line stalls and connection timeouts—and the frozen experiences and support tickets they can cause.
Proxylity keeps packet reception separate from your application. Update the code behind your endpoint without restarting the listener, so your team can release smaller changes and learn sooner.
Your protocol can acknowledge and retry messages that need confirmation, or move on when only the latest update matters. UDP keeps messages independent instead of tying them to an ordered transport stream. Proxylity routes those messages to your AWS services; your application's reliability design can span backend changes without depending on a particular transport session.
Explore the architectureSee it change under load
What would you change if deploying didn't mean disrupting customers? In the live demo, follow a running UDP service while its configuration and implementation change.
The goal: ten changes with zero lost packets. Watch the measurements live and discuss what continuity would require for your workload.
Packet reception runs independently of your application deployment. Supported destinations can send replies through the gateway to your clients.
Bring your use case
Turn device readings into alerts, dashboards, or stored measurements using your AWS data pipeline.
Explore CoAPHandle RADIUS requests with AWS services without requiring your network equipment to switch protocols.
Explore RADIUSCollect syslog messages in AWS for analysis and retention, without maintaining a syslog receiver.
Explore syslogSomething custom? Bring your packet format, traffic pattern, or architecture sketch. We can work through it together.
Continue the conversation
Work through how your packets would reach your application, what happens to replies, and what it would cost. Or start with a live demo if you just want to see it work.
At re:Invent
Bring the question you're trying to answer. Walk through your design with Lee or see a live demo during the conference.
Request an in-person demoOpens your email app with a few prompts. We'll confirm the time and place by email; this is a request, not a reservation.
When you're back
Give your architecture more time after the conference. Bring a colleague and explore the implementation details together.
Choose a video call timeOpens Google Calendar's booking page. Choose a date after the conference and check the displayed time zone.
Prefer email, or no email app configured? Write to team@proxylity.com and mention re:Invent.
Explore after the conference
Try your first device or UDP service with a free listener and your first million packets free each month. Subscribe through AWS Marketplace and keep charges on your AWS bill. AWS destination service charges are separate.