A PAM bastion built for IT service providers and MSPs too
Your technicians work across several clients' infrastructure. With Bastigo, every intervention is limited to a ticket, a duration, and a specific resource, recorded and traceable, with no permanent VPN and no credentials shared across clients.
One intervention per client, never standing access
Whether you deploy one bastion per client or a centralized instance, every technician only reaches the resources listed in their intervention, strictly for the duration of the ticket.
What managing several clients makes harder
One VPN per client, all left open
Every technician accumulates VPN access to several clients, rarely revoked once a job is done.
Duplicated credentials
One credential per client to remember, often stored just about anywhere, with a leak risk that grows with every new client.
Weak proof of intervention
When a billing dispute or incident comes up, there's nothing precise to show for what was actually done.
Hard to secure turnover
A technician leaving the team may have accumulated access at several clients, not always revoked in time.
One intervention per ticket, proof to back it up
One ticket, one intervention
Name the intervention after your support ticket, give it the duration it needs, and the technician only reaches the resource concerned, for that exact window.
Proof of intervention
Every session is recorded: if a billing or incident dispute comes up, the recording factually answers what was done, by whom, and when.
One departure, one less access
A technician leaving the team loses every access in a single action, with no forgotten VPNs or credentials lingering at former clients.
One bastion per client, or centralized at your site
Since Bastigo is self-hosted, both setups are possible depending on how your business is organized.
One instance per client
Installed on each client's own infrastructure, with complete isolation between them: what happens at one client is never visible from another.
One centralized instance
Installed on your own infrastructure, with targets and policies organized by client, for an overall view of your technicians' activity.
What MSPs and IT service providers ask us
Is Bastigo suitable for MSPs and IT service providers?
Yes. An IT service provider or MSP manages its technicians' access to several clients' infrastructure: Bastigo's interventions let you limit each access to a specific ticket, a fixed duration, and a given resource, backed by a session recording.
Can I deploy a separate Bastigo instance per client?
Yes, since Bastigo is self-hosted, an instance can be installed at each client's site (complete isolation between clients) or on your own infrastructure if you prefer to centralize, depending on how you're organized.
Can session recordings serve as proof of an intervention?
Yes, every SSH or RDP session is recorded automatically and replayable: if a client disputes what was done during a billed intervention, the recording provides a factual answer.
How do I manage several technicians across several clients with Bastigo?
Via LDAP/Active Directory (if your technicians are already in an internal directory) or local accounts, combined with policies or temporary interventions that limit each technician to the relevant client's resources, for the duration of their intervention.
See how to organize interventions client by client
Thirty minutes is enough to tailor the demo to your organization.