Skip to content
Bastyx
Book a Demo
Setup guide

Simple to set up. Here’s every step.

One engineer can roll Bastyx out in stages, without an IAM team, new hardware or a migration weekend. Existing access keeps working until you switch it off.

What you won’t need

  • No IAM team
  • No proprietary hardware
  • No application rewrites
  • No new SSH client
  • No big-bang cutover
  • No identity provider migration

Seven steps, from first demo to zero passwords.

  1. 1

    Book a demo

    Fill in the short demo form. An engineer shows you Bastyx live, walks through your laptops, servers, apps, AI agents and identity provider with you, and you agree a small pilot scope together.

    You’ll need
    A rough picture of your team, operating systems, servers and key apps.
    Your team notices
    Nothing yet.
  2. 2

    Choose cloud or on-premises

    Bastyx Cloud is the fastest start, with nothing to operate. On-premises runs the control plane in your own data center or cloud account when policy or regulation requires it. Policies, enrollment and the admin console work the same way in both.

    You’ll need
    For on-premises, somewhere to run it. We share the requirements during setup.
    Your team notices
    Nothing.
  3. 3

    Connect your people

    Bastyx reads people, teams and roles from Okta, Microsoft Entra ID or Google Workspace. Smaller teams without one can manage people in Bastyx.

    You’ll need
    Admin access to your identity provider, or a list of people and teams.
    Your team notices
    Nothing.
  4. 4

    Enroll a pilot team

    Pick one team. Each person installs the Bastyx app on their macOS, Windows or Linux laptop and registers two authenticators, such as the built-in fingerprint sensor and a hardware security key. There’s no password to set, and nobody outside the pilot changes anything.

    You’ll need
    The laptops and phones people already have. Security keys are optional and standard FIDO2.
    Your team notices
    A few prompts, once. After that, a touch or a fingerprint instead of a password.
  5. 5

    Protect your first servers and apps

    Put a first set of resources behind Bastyx: a server group running the bastyx agent, an app that supports SSO and a legacy app through the access proxy or a vaulted credential. The old way in keeps working in parallel while the pilot proves out.

    You’ll need
    An owner for each resource you start with, and sudo on the servers.
    Your team notices
    The pilot team signs in the new way. Everyone else is unaffected.
  6. 6

    Give AI agents their own identities

    Agents that touch your infrastructure stop borrowing people’s tokens. Each one gets its own identity, a named owner, a policy and short-lived credentials, with the owner’s approval required for anything sensitive.

    You’ll need
    A list of the agents and automations that use personal or shared credentials today.
    Your team notices
    Agent owners approve sensitive actions with a touch of their key.
  7. 7

    Switch off passwords and expand

    When the pilot is solid, disable password and static-key login on the protected resources, and let Bastyx rotate any password a legacy app still needs into the vault. Add teams and resources by policy. From then on, offboarding is one action.

    You’ll need
    Nothing new.
    Your team notices
    No passwords to remember, reset or share.

Pilot timeline

Four weeks, one team.

Steps 3 to 7 as a pilot. Requirements and the server-side change are in the developer quickstart.

  1. Week 1

    Identity provider and pilot laptops

    Connect Okta, Entra ID or Google Workspace. The pilot team installs the Bastyx app and registers two authenticators each.

  2. Week 2

    Servers

    Install the bastyx agent on a first server group and grant the pilot team access by policy. Existing keys keep working.

  3. Week 3

    Apps

    Move a SAML or OIDC app to Bastyx, and put one legacy app behind the access proxy or a vaulted credential.

  4. Week 4

    Parallel run and switch-off

    Run old and new access side by side, offboard a test user, check the audit log, then switch off passwords and static keys for the pilot.

Deployment

Cloud or on-premises.

Same policies, same console, same sign-in for people. The difference is who runs it and where your data lives.

  • Who operates it

    Bastyx Cloud
    Bastyx
    On-premises
    Your team, with our support
  • Where the control plane runs

    Bastyx Cloud
    Bastyx Cloud
    On-premises
    Your data center or cloud account
  • Directory and audit data

    Bastyx Cloud
    Stored by Bastyx
    On-premises
    Stays in your environment
  • Legacy-app proxies and vaults

    Bastyx Cloud
    Next to your apps
    On-premises
    Next to your apps
  • Updates

    Bastyx Cloud
    Applied by us
    On-premises
    Applied on your schedule
  • Best for

    Bastyx Cloud
    The fastest start
    On-premises
    When policy or regulation requires it

Go deeper

Guides for what you’ll protect

FAQ

Setup questions

How long does a pilot take?

Four weeks for one team, one server group and a couple of apps: identity provider and laptops in week one, servers in week two, apps in week three, then a parallel run and switch-off in week four.

Will anything break during the rollout?

It shouldn’t. Existing access keeps working in parallel, and each resource switches over only when you turn off its old login.

Who needs to be involved?

One engineer to run the rollout, an owner for each resource you protect, and the pilot team. Bastyx doesn’t need an IAM team or outside consultants.

Do we need to buy hardware?

No. Passkeys work on the laptops and phones people already have, and standard FIDO2 security keys work if you want them. We recommend hardware keys for admins and production access.

Can we run Bastyx on-premises?

Yes. The control plane runs in your own data center or cloud account, with the same policies, enrollment and console as Bastyx Cloud.

Start with one team.

Book a demo, see Bastyx live, and we’ll plan the rollout with you.