Locked until you say so
A newly published tool is open to nobody until you invite people.
In practice: Publish on Friday, invite people on Monday. Nobody stumbles across it in between.
Safe by default
How PeerLink keeps your tools private
The safe settings are the defaults, so you don’t need to be a security expert to share a tool.
Your work sign-in, nothing new
People sign in with the account your company already manages. Your tools never see or store a password.
In practice: When someone leaves the company, their work account is closed, so they can’t sign in to your tools again.
Every tool kept separate
Each tool runs separately, at its own address. One tool can’t read another tool’s information.
In practice: Your expense tracker and your party sign-up sheet never share anything.
Remove access instantly
Take a person or group off a tool and their next request is refused.
In practice: A contractor’s project wraps up? Remove them in seconds.
Guests see one thing only
Invite someone from outside your company and they reach only the tools you shared with them.
In practice: A client can see their project portal without ever seeing your internal tools.
A paper trail, automatically
Every change to who can use what is recorded: who did it, to whom, and when.
In practice: “Who gave the agency access?” has an answer, without anyone having to remember.
For your IT team
Technical details for IT and security teams
Your IT or security team will want specifics. They’re listed here, or you can forward them this page.
Send this page to IT- Single sign-on through your OpenID Connect identity provider; apps never handle credentials.
- Deny-by-default access: no grant, no entry. Only allowlisted members can publish or administer.
- Every app runs isolated on its own hostname, behind one proxy that is the only route in.
- Identity reaches apps as a header the proxy sets, and any copy a browser sends is stripped first.
- Runs in your own Google Cloud project, as a dedicated deployment for your organisation.
- Audit trail of access changes, plus a sign-in attempt log for platform admins.
- Personal API tokens for the CLI and agents: named, individually revocable, stored only as hashes.
- App data is restored on start and continuously replicated to Cloud Storage by the platform.
- Automated checks against platform policy before every publish, on the laptop and again server-side.
Want to try PeerLink with your team?
PeerLink is in early access. Tell us what you’re building and we’ll get you set up.