Security: Every access visible. Every rule yours.
Weldall sits between AI agents and your systems. It checks every request against central permissions and logs every access, granted or denied.
- Grantedcontracts:readContracts09:41
- Grantedcontracts:updateContracts09:42
- Deniedhr-server:readHR server09:44
- Grantedcrm:readCRM09:47
- Grantedbilling:readBilling09:48
Built by the Seibert Group.
ISO/IEC 27001:2022
The Seibert Group’s information security management system is certified. The certificate and Statement of Applicability are in the Trust Center.
Information security guidelineGDPR
The Seibert Group has appointed a data protection officer. The Trust Center lists documents on data breach notification and data protection impact assessments.
Trust CenterWhat Weldall stores
Weldall stores configuration, audit records and encrypted connection credentials in PostgreSQL. The agent only gets the response data.
Weldall docs
No credentials on the agent.
Sign in with your identity provider
Weldall has no local accounts. Employees sign in with your company’s existing OIDC identity provider.
The agent never sees a token
The CLI keeps the session and device key in the operating system’s secure credential store and sends requests itself. The agent only gets the response data.
Short-lived, device-bound tokens
Access tokens are short-lived and bound to the device key with DPoP. Refresh tokens rotate on every renewal, so a used one is worthless.
Open standards and drafts
OAuth 2.0 with PKCE, DPoP (RFC 9449) and the IETF draft Identity Assertion JWT Authorization Grant (ID-JAG).
Security model in the docs
The standards in brief.
Two short videos on ID-JAG and DPoP, the two mechanisms behind sign-in and tokens.
Identity Assertion JWT Authorization Grant
The IETF draft that carries a single sign-in down a trust chain.
Demonstrating Proof of Possession
The mechanism (RFC 9449) that makes a token worthless without the matching key.
You decide who can do what.
Permissions per person
Admins set in one place which scopes each person can use. The authorization server decides whether each request is allowed.
No access without a grant
Signing in with the identity provider grants no access by itself. An admin assigns access before the first sign-in.
Registered services only
Before each request, Weldall checks that the target belongs to a registered service and that the scope is supported and granted. For SaaS tools such as HubSpot, Weldall also filters by REST endpoint and applies its own policies.
Permissions as code
Scopes, services, skills and assignments can live as YAML in a Git repository. weldall plan shows every change before it’s applied.
Infrastructure as code in the docs
Connections you control.
Personal connections
Each person connects their own account and approves access. A connection belongs only to that person.
Permissions chosen by admins
Admins choose which permissions a connected system offers. Users can approve only those.
Encrypted on the server
Provider credentials use envelope encryption, with the key in the server environment or in OpenBao. They never reach the person’s device.
Revocable
Remove a connection at any time. For Google, Weldall also tries to revoke access.
Run Weldall where it suits you.
Self-hosted
Run Weldall as a single container in your own infrastructure. It runs without root privileges and stores configuration, audit records and encrypted credentials in your PostgreSQL database.
Setup guideOperated by the Seibert Group
Prefer not to run Weldall yourself? The Seibert Group runs it for you.
Talk to our engineers
Open to inspection.
Public source code
The CLI and server source code is public on GitHub under the Functional Source License. Each version converts to Apache 2.0 after two years.
Source on GitHubReport a vulnerability
Found a vulnerability? Report it to security@seibert.group. The Seibert Group runs a vulnerability disclosure program.
Security at the Seibert Group
Questions and answers
Does the AI agent get access to our credentials?
No. The agent never receives an access token and stores no credentials. The Weldall CLI sends the request itself and returns only the response data. Tokens are short-lived and bound to the person’s device with DPoP.
Which identity providers are supported?
Any OpenID Connect provider, such as Google Workspace, Okta, Entra ID, Keycloak or Auth0. Weldall has no local accounts and no passwords. Signing in alone grants nothing. An admin assigns access by email address or group.
What happens if a token is stolen?
A stolen token alone is of little use. Access tokens are short-lived and bound to the device key with DPoP, so they won’t work on another machine. Refresh tokens rotate on every renewal, so a used one is no longer valid.
How quickly can we revoke access?
Weldall checks group membership with the group provider on every access decision, without caching. Anyone removed from a group or a scope loses access at the next decision. Deactivating a machine client or removing its grants stops new tokens immediately, and issued tokens expire within five minutes.
Is our data used to train AI models?
Not with SeibertGPT, the Seibert Group’s model hosted in Helsinki (EU). Prompts and answers are never used for training, and API request contents aren’t stored. If you use your own models, your agreement with that provider applies.
Security review