edgesocketEnergy & renewables
Remote maintenance access to edge gateways and field computers at solar and wind sites, energy monitoring installations and EV charging locations. Reach existing web panels or maintenance services.
Explore energy access →
FOR ENERGY & INDUSTRIAL IOTCore built · in development
Your field edge.
One direct link.
From energy sites to production lines, reach services on your edge devices over secure, encrypted connections. We’re building EdgeSocket with flexible cloud and on-premises options for different field requirements.
Encrypted end to endCloud + on-premisesWorks with your tools
FOLLOW YOUR CONNECTIONInteractive diagram
Direct data path
Service traffic travels between your two clients. Signaling carries no application payload.
Control & authorizationEncrypted service traffic
*When a direct path is available. On restrictive networks, an authorized relay server steps in. The diagram illustrates connection paths.
WORKS WITH THE TOOLS YOU ALREADY USESSHPostgreSQLHTTP / APIsRDPDNS / UDP
BUILT TOWARD REAL FIELD NEEDS
From energy sites to production lines.
We’re developing remote access for industrial IoT gateways, field computers and distributed edge devices. The goal: reach the service you need, with access tied to the right person and device.
Manufacturing & industrial IoT
Access existing services on machine-data gateways and industrial PCs across production lines. A device-based access model for maintenance teams and authorized service partners.
Explore industrial edge access →Logistics & retail
Reach local applications and edge services across warehouses, distribution centers and stores. Support geographically distributed sites through authorized device access.
Buildings, utilities & agriculture
Access gateway interfaces and local edge applications in building automation, water management and agricultural monitoring. Keep using the tools and services already deployed in the field.
Target use cases for a product in development. Device and protocol compatibility will be assessed for your setup.
Tell us about your field setup
01 / CONNECTION, REIMAGINED
Let your peers
Let your peers
do the talking.
EdgeSocket first checks who you are and what you may access, then introduces your devices. Data flows encrypted between the devices themselves. Your service stays yours.
Identify. Authorize.
Both you and your devices are verified separately. Access to the target device is checked before the session starts.
Find a direct path.
The system tries the possible network routes between your devices and picks the shortest one that works.
Connect your service.
Your service’s data travels through an encrypted channel. If a direct connection is not possible, an authorized relay server steps in.
WHEN DO YOU NEED TURN?Illustration
Try direct. Relay if needed.
First, find each other.
Signaling introduces the authorized peers. STUN helps discover public addresses; ICE checks connection candidates.
DTLS encryption on both paths
Illustration, not a live connection. TURN requires an available relay and access permission.
Direct first. Relay when needed.
BUILT FOR THE EDGE
Small footprint.
Small footprint.
Solid foundations.
Focus on your devices and services. We’re bringing connectivity, access control and relay when needed into one platform.
Peer-to-peer at the core.
Your devices connect to each other directly whenever possible, and everything they exchange is encrypted along the way.
Direct & encryptedRemote feels local.
Reach SSH, databases, internal tools, or remote desktops as if they were on your own computer. Your existing service login stays in place.
Your tools. Your workflow.The right device. The right person.
Home owners reach their own devices; enterprise team members need an explicit device grant. Details are in the access section below.
Device-level authorization
02 / ACCESS IS A DECISION
Your devices.
Your devices.
Your rules.
A session name is not permission. Every connection belongs to an identity, an account, and a target device.
- Isolated home and enterprise accounts
- Explicit per-user device grants
- Revoke access to close active sessions
access.policyIllustration
01 / ADMINISTRATOR
Assign device access
The administrator grants Ege Meriç Erdoğan access to factory-edge within the organization.
02 / USER’S DEVICE LIST
EME
Ece Melis ErdoğanAccount owner
Authenticated
home-gatewayYour account · SSH / HTTP
home-storageYour account · TCP services
Connect to edge devices registered to your own account. Enterprise accounts provide per-user device permissions for team access.
03 / THE EDGESOCKET APPS
Choose your edge.
Choose your edge.
Reach your service.
One clear design across web, desktop and Android. Search devices and services, follow connection status and manage team access. Use the desktop and Android apps in Turkish or English.
Explore the actual screens →Open your existing SSH app through a local connection.
An EdgeSocket app runs at both ends. The app manages the connection; your service’s own login remains in place.
edgesocket.Connection illustration
01
CHOOSE AN AUTHORIZED DEVICEfactory-edgeExample device · explicit user grant
02
CHOOSE YOUR SERVICESSH
TCP · 22
03
OPEN A LOCAL CONNECTION
127.0.0.1:2222
Preview: choose a service, then follow the connection flow.
Flexible deployment. One connection experience.
Use the cloud option or deploy the complete system in your own environment to meet your organization’s needs. Our goal is the same straightforward app experience for reaching authorized edge devices in either setup.
01Cloud deployment option
02Full on-premises when needed
03A simple app for everyday access
Both deployment options are part of the product plan. EdgeSocket is still in development; general access is not open yet.
WHAT WE’RE BUILDING FOR YOU
Connect with less effort.
Connect with less effort.
Stay focused on your work.
The connection core, desktop and Android apps, and account console are in development. Current interfaces share a consistent design; managed service plans have no committed launch date.
Reach your devices securely
- Direct device-to-device connections
- Encrypted relay when needed
- Access to your existing services
- Home ownership and team device permissions
One app, a clear path
- Sign in with your account
- Find the devices you can access
- Choose a service and connect
- See connection status and helpful guidance
Cloud or on-premises
- Access through the cloud
- Full-system on-premises deployment when needed
- Organization and team access
- Relay packages suited to your needs
UNDER THE CONNECTION
WebRTC. Beyond video calls.
WebRTC, the technology behind video calls, can carry application data too. EdgeSocket uses its encrypted data channels to connect the services you already run.
01Your serviceSSH · SQL · HTTP · DNS
02Data channel / SCTPCarries streams and datagrams
03DTLSEncrypts data between peers
04ICE · STUN · TURNFinds a working network path
Your protocol stays familiar.
Your app connects the way it always does, to a local address. EdgeSocket carries the data through an encrypted channel and hands it to the service on your edge device, preserving order and reliability where your protocol expects them.
Discovery first. Relay when needed.
The system first looks for a direct path between the devices. If none works, a configured relay server (TURN) forwards the encrypted packets. Path discovery never carries your service traffic.
Permission follows the device.
Both you and your devices are verified. Permissions are granted per target device, and every part of the connection enforces the same policy. Revoking a permission closes active sessions. Access covers the whole device, not individual ports.
A FEW GOOD QUESTIONS
Let's make it clear.
Does my data always travel directly?
The connection tries the direct path first. When it works, your data flows straight between the devices with no middleman. When it does not, an authorized relay server can carry the encrypted data. A paid relay package is required to use the built-in commercial relay.
Do I need the app on both sides?
Yes. The field device and your computer each run an EdgeSocket app. In the desktop app, choose an authorized device and service to connect. You can keep using your existing SSH, database or web app.
Can I limit access to individual services?
You choose which service you connect to. Authorization currently applies to the whole device, not individual ports or services. Service-level policies require a separate future design; the service's own login remains important.
Will on-premises deployment be available?
Yes. We’re planning flexible cloud and on-premises deployment options. On-premises will let the complete system, including management and connectivity components, run in your own environment. Share your use case and requirements with us.
Is the platform available yet?
Not for general use yet. The connection core is implemented; we’re working toward the cloud platform and end-user app. Leave an early-access request or share your use case.
LET’S BUILD WHAT YOU NEED
Not quite ready. Ready to listen.
EdgeSocket is still in development. Tell us what you want to connect, leave a question, or request early access. We can contact you about your request at the email you provide.
- Tell us your use case
- Share the devices and services you need
- No account or payment required
This is a request, not an active account or a promise of an access date. Please do not include passwords, access keys, or other secrets.