Geo-scale, next-generation peer-to-peer sharing platform built on top of OpenZiti.
Go to file
2022-07-27 14:45:16 -04:00
.github/workflows
bin authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
cmd/zrok authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
controller authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
docs/images fixed diagram; wthwit? 2022-07-21 21:30:49 -04:00
http tunnel service call wiring (#3) 2022-07-26 16:00:59 -04:00
proxy logging lint 2022-07-27 12:58:16 -04:00
rest_client_zrok authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
rest_model_zrok authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
rest_server_zrok authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
specs authentication; enable only (for now) (#11) 2022-07-27 14:45:16 -04:00
util adjust reverse proxy infrastructure to selectively proxy based on host header (#7) 2022-07-26 13:30:19 -04:00
zrokdir service policy (#3) 2022-07-26 17:17:37 -04:00
.gitignore controller store skeleton; sqlx; sqlite3; migrations 2022-07-22 13:53:39 -04:00
go.mod rough and sketchy identity creation and enrollment 2022-07-26 12:26:58 -04:00
go.sum rough and sketchy identity creation and enrollment 2022-07-26 12:26:58 -04:00
README.md

zrok

zrok is a utility for quickly proving public access to dark, private applications.

zrok overview

zrok is designed with the following properties:

Easiest Possible On-ramp

zrok is the fastest, simplest path for exposing dark, private applications onto the public internet using Ziti.

Simple Registration

Registering for access to zrok should provide the user with a single identity token, which can be used from any shell environment to quickly enable access to private applications.

Enabling zrok in a shell should be as simple as executing something like:

$ zrok enable <token>

Single-Executable Deployment

A registered user should only need a single executable (zrok), along with their identity, to enable zrok capabilities in any shell environment.

URLs that Don't Change

The smallest, simplest zrok implementation could be capable of providing URLs that don't change. The competition does not offer this capability without a subscription.

Expand into Ziti

The zrok implementation should (ideally) be such that zrok usage patterns can co-exist with larger, more featureful Ziti implementations. Ideally, a developer who started with zrok should have patterns that allow them to incrementally expand their usage.

Multiple Isolated Tenants

A single zrok implementation should support multiple isolated tenants coexisting on the same deployment (and underlying Ziti network) in a secure manner.

Self-hosting Capable

The zrok implementation should support self-hosting, such that existing Ziti users can easily add zrok capabilities to their existing networks.