TQAccess
One controlled door to every server and database your team administers. From the browser or from the terminal your team already uses, with no scattered keys and no shared passwords.
Nobody knows who connected where
In most companies, server access grows by accretion: a key here, a shared password there, a VPN for the ones that came later. It works until somebody asks a simple question.
Who connected to production last Tuesday, and what did they do?
Keys scattered everywhere
Private keys live on laptops. When someone leaves, they have to be hunted down server by server.
Shared accounts
Several people using the same user. The log says what happened, never who did it.
Exposed ports
Every server reachable from the internet is one more surface to defend and to patch.
No usable record
When an auditor asks for access history, the answer is assembled by hand, if at all.
Every connection through one place, and recorded
TQAccess sits between your team and your infrastructure.
Terminal in the browser
Full SSH sessions from any browser, with tabs for working on several servers at once, or from your own client.
Databases too
MySQL and PostgreSQL sessions through the same door, with the same record as a shell session.
Keys that never leave
Credentials are held by the bastion. Your team connects without ever holding a private key.
Separated environments
Production, testing and each client kept apart, so nobody reaches what they should not even by accident.
Live sessions
See who is connected right now, from where, and close a session that should not be open.
File transfer
Upload a file to the server from the same window, and export the session when it ends.
The same door, whichever way you come through
Control usually fails because it is inconvenient. If the only way in is a web page, the people who live in a terminal will find a way around it.
So TQAccess does not force anyone to change how they work.
From the browser
Full sessions with tabs, file transfer and nothing to install. Useful from a borrowed machine or a phone.
From your own terminal
Connect with the SSH client you already use and you land on a menu, not on a shell. Nobody reaches a command line without passing through it.
Organised by environment
The menu groups what each person may reach, separated by client and by environment, and shows only that.
One keystroke to connect
Search, select, enter. The credentials are applied by the bastion, so nobody types or stores a password.
The answer to the audit, ready in advance
The value is not the terminal. The terminal is the easy part.
The value is that afterwards there is a record: every session, who opened it, to which server, for how long.
Offboarding in one step
Someone leaves the company: you revoke one bastion user, not keys spread across every server.
Named responsibility
Each person connects as themselves, even when the server user is shared. The record keeps both.
Usage visible
Which servers are worked on most, by whom and for how long. Useful well beyond security.
In daily use
TQAccess is how we administer our own platforms and our clients' infrastructure, every day.
Let us talk about your project
Book a meeting and we will show you the system working on a real case, not on slides.
Request a meeting