Your software workloads at your finger tips
The NearEDGE's solution is built around 3 types of entities
- Workloads, a combination of your software and the NearEDGE access agent
- Control center, responsible to manage the basic operation of the agents. It resides in your data center or in our cloud
- Access gateways providing secure remote connectivity to workloads. The gateways always reside in your data center
The workloads run as container or inside a virtual machine or even as a regular software on a physical machine. The agent enables TCP connectivity to any service inside the workload. Using this connectivity, you can:
- SSH / Login into the workload
- Perform remote packet capture, directly from the workload into your packet analyser, such as wireshark
- Monitor processes, including using a local generic monitor tool, such as zabbix, etc.
- Troubleshoot application performance with OpenTelemetry, gprof, pprof, etc.
- Debug your service using a remote debugger, such as gdbserver, delve, jdwp, debugpy
- Etc.
Boost the productivity of your team. Learn howto perform specific tasks, such as debugging, wiresharking, etc.
The NearEDGE access agent integrates seamlessly in your existing CI/CD pipeline and/or orchestration methodology. It comes complete as a single fully statically linked binary file. It is delivered as
- Container image, complete with the agent and some support functions, such as busybox, sshd and tcpdump. You can consume this image:
- Directly as a standalone container
- As a sidecar, attached to your pods
- In the CI/CD pipeline, extracting the agent into your own container image
- Download file, which you simply need to copy to a target host and execute.
The agent operates with the following characteristics:
- Does not expose any ports
- Only uses outbound HTTPS connections
- Traverses proxy
- No installation procedure needed
- Does not need root privileges
- Hardened
See how the agent and Access gateways are easy to deploy with our step-by-step guides.
We architected the solution so that it integrates into any type of build, deployment and/or orchestration scenarios. This user first approach requires no deep knowledge not already present in every devOps teams.
In order to be agnostic from the deployment environment, the solution was created with the following design considerations in mind:
- No plugin required
- No opening of firewall rules (normal Web traffic)
- No use of special features, such as packet mirroring
- No API calls
- Your own credentials
- No local configuration other than some form of host/instance name
Despite being easy to use and very low friction, security was not sacrificed. At NearEDGE, we believe in the perimeterless paradigm and therefore always assume a potential hostile environment. Entrenched into the design, we included:
- Double encryption, using transport and application level
- Stronger key length than normally used (4096 vs 2048 or even 1024 bits)
- No sharing of your credentials to us
- Your data never touches the control center nor our cloud