Developers, DevOps, IT, Support - simplify your workflow and work faster

Developers should be able to embed secure connectivity into their applications, removing the reliance on network configurations.  The benefits of this approach include reduced cost, fewer field calls, greater availability, and easy remote support, provisioning, and configuration.

92% of enterprises have a multi-cloud strategy; 80% have a hybrid cloud strategy.  Hybrid and multi-cloud support the best of breed, increase agility, and improve the bottom line. Developers need to connect to multiple locations at once. Today's modern continuous integration (CI) and continuous development (CD) pipeline includes source code control, build and test automation, release automation, and finally a deployment stage.

The same is true for DevOps and IT teams that need to manage development, test, and production environments as well as devices scattered around the world.

VPNs were created over twenty years ago to connect remote workers to an organization's data center. Since then, cloud applications, BYOD, and a prominent work from home environment have changed the world. Users access resources using devices, networks, and software that the IT team has no control over and is likely unaware of.

Today's developer is on the move working from home, the company office, shared workspace, or an Airbnb.  VPNs create the following issues:
‍
  • VPNs are not always on and developers need to add one extra step to the login process.
  • Due to IP routing limitations with VPNs, developers can't connect to two VPNs at the same time to avoid subnet collisions.
  • VPNs route all traffic through a centralized location/server so scaling VPN hardware is a burden.  It's either expensive with hosted solutions or time-consuming and a possible security vector for having unpatched VPN services and agents.
  • Developers have to talk to IT or DevOps to add IP addresses to the Access Control List.  Alternatively, some organizations allow developers to update the Allowed/Whitelist on their own which reduces the number of employees in the process but could lead to security threats.
  • VPNs can be set up in a “split-tunnel” where private IP addresses route through the VPN but public IP addresses route through your own internet connection.  This means that your public IP address changes when you are at a coffee shop even when on a VPN.  It is also a false sense of security because you believe you are using the VPN 100% when in fact you are not.
  • Some MySQL databases only have a public endpoint such as an AWS RDS MySQL setup for public access.  VPNs can't solve this problem.
  • If you need to grant public access to some users, you will still need to have an access list. Now you are managing a VPN and an Access List.
" I like the idea that when using Remote.It, not all resources are up at the same time.  I have them prepped, so I can connect to them, but they're not actually connected.  Versus a VPN, you're virtually opening a pipe to your entire network, all the time," said Sr Software Engineer & Remote.It customer.  "With Remote.It you have all these options for connections to services, but you're only actually connected to the one you're actually using."

Why do VPNs fail today?

VPNs are difficult to manage and scale. In addition VPNs are very expensive.
Learn more

Full Subnet Access

VPNs provide full network access to networks and subnets. Malware or a compromised account has nothing stopping them from moving laterally across the entire infrastructure causing harm.

User Experience

VPNs create a terrible user experience.  Users go to a cloud application only to have the page timeout before realizing their laptop is no longer connected to the VPN. Additionally, VPNS become traffic bottlenecks and reduce transfer speeds.

Scalability

VPNs are hardware based. During the initial work from home spike, companies raced to increase VPN capacity by buying and deploying additional VPN gateways.

Multiple Connections

VPNs don't allow multiple connections at the same time to multiple cloud environments and the corporate data center.
Developers access remote repos, databases, application including multiple networks at once using Remote.It

Benefits of using Remote.It

Connecting devices that were previously inaccessisble
Get Started
With Remote.It you'll be able to :
Devices remain on a private network. No public IP address is needed.
Connect to devices that were inaccessible before like device on CGNAT networks without a public IP address.
Devices not exposed on the public Internet. No port forwarding required.
Connect to multiple cloud environments at the same time including local Git repositories, Azure, Google, and AWS.
Improves security by removing over-privileged access found with IP/subnet based VPN solutions.  Implement a least privileged access model with granular sharing permissions by service and protocol. Devices are not scannable by malicious bots since no ports are open.
Invite users via email address without managing IP addresses, access control lists, IAM roles.
Scales without any hardware requirements
Build remote access into your application or device
Extensive APIs allow for embedding all Remote.It functions into your application or device

OEM & Enteprise Plan

Plans available for all use cases including connecting to remote devices in over a hundred countries to embedded solutions for applications and device manufacturers

Custom and non-standard Linux and device packages

Standard plans include applications and device packages for common operating systems and devices such as Linux, Windows, Mac, RaspberryPi, AWS, iOS, Android, OpenWRT, Jetson, LoRaWAN, Dragino, and more. OEM plan provides custom builds.

Dedicated Proxy Server

Single tenant proxy server to simplify firewall rules at target network for locations with very strict rules such as blocking all UDP outbound traffic.
Remote.It used to monitor automotive sensors over 5G

How do developers access AWS resources using Remote.It

Remote.It will map network connections such as AWS cloud services to a local address for developers to use. Here are some examples.

Secure Shell (SSH)

Connect directly via command line to any service or server

Database

Connect to databases such as Redis, RDS or DynamoDB

HTTPS/HTTP

Connect to web applications

Remote Desktop

Remote desktop into servers such as Windows EC2 instances
Learn more
Developers connecting to remote repos, applications, databases as if they are local

Request a demonstration or contact us about your specific requirements!

We envision a world where the connection is the network: cloud services, connected devices and endpoints, easily and securely connect to each other, any time, anywhere.
Solutions
DevicesOEMDevelopersGaming
Product
Getting StartedPricingDownloadTechnology
Company
AboutContactCareersLegal
Resources
BlogPress ReleaseVideosCase Studies
Documentation
UsersDevelopers
Support
Help CenterCommunity ForumContact Support
© remote.It, Inc. All rights reserved.