Security
Bstrapr helps teams give people controlled access to private infrastructure without turning shared credentials into the access model. Your environments remain under your ownership; Bstrapr manages the relationship between people and the Sites they are allowed to reach.
Users authenticate through Bstrapr before reaching assigned Sites. Access is tied to an identity in your account rather than relying on shared passwords as the collaboration model.
Traffic to enrolled Sites uses encrypted connectivity via a VPN client that dials outbound to the Bstrapr control plane with a one-time auth key — no inbound firewall changes are required on infrastructure you own. Connectivity protects the path; Bstrapr adds the authorization and lifecycle controls around that path.
You enroll infrastructure you already operate — cloud VMs, remote servers or designated machines. Enrollment establishes a Site under your ownership; Bstrapr does not take over your hosting provider.
Access grants are scoped to Sites and environments. A person can be limited to one authorized environment while your core team retains broader access.
When access is revoked, Bstrapr-mediated access for that person ends while the Site remains enrolled and under your control — no rebuild required to end an engagement.
Accounts, Sites, and access relationships are isolated by customer context so one team’s collaborator model does not bleed into another’s.
Bstrapr manages enrollment and access relationships. Application data, source code, and workloads remain on infrastructure you operate, subject to the exact behavior of enabled workspace and documentation features.
Review who was granted access, which Sites they could reach, and when access changed. That history supports day-to-day accountability for lean teams and agencies.
This is described as access activity history — not an audit or compliance control — until immutable evidence retention and formal compliance controls are in place.
Operational responsibility for the shared platform is ours; responsibility for your enrolled Sites and workloads remains yours. Dedicated deployments can define support and operational boundaries explicitly — see Dedicated or contact us.