Which tier do I need?
Community, until somebody else has to sign in. The week you need directory
sign-in, more than one approval policy, PostgreSQL behind more than one controller,
workers reaching fleets a single machine cannot, or a change register an auditor will
actually read, that is Team. Enterprise is for when the proof has to come from outside
your own install: an independent witness countersigning your history, custody that
outlives your own retention, and people on the hook on your audit calendar. Most
organizations should start on Community and let the gate tell them when they have
outgrown it.
Can I move from AWX?
Yes, on Community, in one command, and the same goes for Semaphore, Rundeck,
Jenkins freestyle jobs, and plain crontabs. AAP, Tower, and Ascender share the AWX
export format. For a large or regulated move, the
Migration Program does it for you.
Start with the switching guide.
I started on SQLite. How do I get to Postgres and HA?
Team includes Postgres. Today the supported move is switchtender backup
and restore, which carries your configuration: projects, templates,
inventories, credential shells, schedules, and tokens. Run history and the audit
chain stay with the SQLite file, and that is not a loss: the old database remains
readable and its evidence verifiable forever, because receipts never depend on
where the data lives now. If you want the history physically merged, tell us and
we will do the move with you.
How do I buy or trial today?
Email hello@switchtender.com
with your org name and band. A signed 30-day trial license usually lands within
hours, no card. Buying works the same way with an invoice until card checkout ships.
Enterprise starts with a conversation.
Do you count my hosts?
No. Bands are self-reported at purchase, the binary counts nothing and reports
nothing, and we will never ask to audit. If your fleet grows past your band, we trust
you to move up at renewal, and that trust is priced in.
What happens when a license lapses?
Paid features stop; nothing else changes. Your data, your evidence, your receipts,
and every Community feature keep working, the running server drops to Community
without a restart, and a database you initialized on PostgreSQL stays fully usable
forever. We built the gate so that it cannot hold your data hostage even if we
wanted it to.
Why is the change register paid when receipts are free?
Because proofs and packaging are different things. Anyone must be able to verify
what your install did, on any tier, forever, or the evidence story is worthless, so
the chain, anchors, receipts, dossiers, and verifier are all Community. The period
change register is the assembled compliance deliverable an auditor consumes, and
assembling deliverables is a thing organizations pay for.
What does the license allow?
SwitchTender is source-available under BSL 1.1. You can read the source, modify it,
self-host it, and run it in production for your own organization. The restriction is
offering it as a competing hosted service. Each release converts to Apache 2.0 two
years after it ships. See the LICENSE for the exact terms.
What exactly is the license file?
A small signed JSON document. The binary carries our public key and verifies the
signature offline; nothing is fetched, ever. Install it with
switchtender license install, see where you stand with
switchtender license status. No license server, no activation, no
phone-home, and losing internet changes nothing.
What happens to paid features if you disappear?
Your license keeps verifying, because verification is offline, so everything works
through the end of your term, and nothing you produced is ever lost: Community, your
data, and your receipts work forever, and the open verifier does not depend on us.
Each release also converts to Apache 2.0 two years after it ships, so the code
itself outlives the company.
