Browser-first control
The controlling side is designed to work in a modern browser. Only the computer being controlled needs an agent.
In developmentControl Beyond Distance
The browser becomesyour control surface.
Telekratos is building a precise, security-focused way to reach the computers you trust—from a modern browser.
01Browser control02Explicit session03Trusted agent
Telekratos / ControlSelected deviceAster-01
Identity verifiedDesigned from first principles
Distance becomes infrastructure—not friction.
The product direction is built around four deliberate choices. Their current status remains visible.
Trusted devices
A permanent, understandable list is planned for computers you own or are authorized to administer.
In developmentExplicit authorization
Device enrollment and session access are intended to be visible security events—not hidden background actions.
PlannedDirect when possible
The architecture aims to use WebRTC peer connectivity first, with a managed TURN relay when networks require it.
PlannedPlanned workflow
Trust first. Connection second.
A deliberate sequence from owner-managed software to a visible, revocable session. This workflow is not yet publicly available.
- 01
Install the agent
Place the Telekratos Agent on a computer you own or are authorized to administer.
- 02
Link the device
Enroll the computer to create a clear, persistent trust relationship.
- 03
Open your browser
Choose a trusted device from a modern browser—without installing controller software.
- 04
Authorize a session
Start a visible, revocable remote session through the planned secure connection flow.
03 / Product vision
One secure space for the computers that matter.
No controller installation. No ambiguous device state. A focused browser experience designed around known endpoints and explicit session authority.
Browser surfaceTrusted inventoryVisible authority
Planned security model
Authority should be visible at every boundary.
These are architectural goals—not claims of production completeness or independent certification.
Explicit enrollment
A device enters the trusted space through a visible, authorized process.
Short-lived authority
Session access is intended to expire cleanly and remain revocable.
Known endpoints
Users and devices are planned to prove identity before coordination begins.
Useful audit events
Security-relevant actions should remain understandable after a session ends.
Connection model
Coordination stays visible. The session takes the shortest trusted path.
The planned architecture separates session coordination from the remote stream, preferring direct WebRTC connectivity and using a relay only when the network requires it.
Architecture direction / not production availability
AControl surfaceModern browser
No controller installation
BTrusted endpointTelekratos Agent
Owner-managed software
Introduces authorized endpoints and negotiates the session.
Provides a controlled path when direct networking is unavailable.
Authorized use
A clear boundary: only the systems you are allowed to reach.
Telekratos is intended for computers you own or have explicit permission to administer. The product direction does not include covert access.
Workstation
Reach a computer you own or administer when work moves elsewhere.
Home system
Access personal applications through a device you have explicitly trusted.
Assisted support
Help someone through a visible, authorized permission path.
Small-team fleet
Maintain a focused inventory of known computers without hidden monitoring.
Development transmission
Built in deliberate stages.
No release dates are being announced. Status labels describe the current direction and may change as engineering progresses.
Foundation work active
Foundation
In developmentDevice enrollment
In developmentSecure signaling
PlanningRemote viewing
UpcomingRemote input
UpcomingPrivate beta
UpcomingFrequently asked
Clear answers, before the beta.
Telekratos is still being built. These answers reflect the current product direction without presenting planned work as available.
01What is Telekratos?
Telekratos is a browser-first remote access and trusted device management platform currently in development.
02Does the controlling computer require installation?
The intended controller experience runs in a modern browser, without a separate controller installation.
03Does the remote computer require an agent?
Yes. The computer being controlled will require a Telekratos Agent that its owner or administrator can manage.
04Is Telekratos currently available?
Not yet. The product is in active development and remote sessions are not publicly available.
05Will Telekratos support Windows?
Windows support is part of the product direction, but supported versions and release timing are not confirmed.
06How will connections work?
The planned architecture coordinates sessions through secure signaling, prefers WebRTC peer connectivity, and uses TURN relay fallback where necessary.
07Will Telekratos be free?
Pricing has not been decided. No free tier, paid plan, or release price is being announced yet.
08How is security being approached?
The planned model emphasizes explicit enrollment, authenticated users and devices, short-lived sessions, revocation, and auditable security events.
Stay close to the build
Control beyond distance begins with trust.
Return for verified engineering updates, security notes, and future early-access information.
Review development status→