Self-hosted means exactly that
Most AI tools for product teams connect to your Jira, Confluence, documents, and all of the data flows through someone else's servers. They process it, their databases store it, their logs record it.
BA Star works the other way around. You deploy it inside your infrastructure. It connects directly to your tools, your data is stored in your environment and nothing routes through us. The context selected for each task goes from your deployment straight to the AI provider you choose.
- All your Jira tickets and project data
- Your Confluence pages and documentation
- Your codebase and architecture docs
- Meeting transcripts and requirements docs
- All generated sessions and artifacts
- Integration credentials, encrypted at rest
Deploy your way
Choose a single binary, a Docker image or a Helm chart.
Deploy on your cloud or your own servers.
Docker & Docker Compose
The fastest way to get started. Pull the image, set your environment variables, run. Works on any Linux host in minutes.
Helm Chart (Kubernetes)
For teams running AWS EKS, Azure AKS, GCP GKE, or self-managed Kubernetes. Full Helm chart with configurable values.
Single Binary
A single compiled binary for Linux (x86_64 and arm64). Drop it on any server, point it at a PostgreSQL database, and start.
Built for European and enterprise
compliance standards
Because BA Star processes nothing on our servers, the standard GDPR data processor concerns do not apply to normal operation. Your data never reaches us.
We provide a Data Processing Agreement covering the narrow case where you might need to share logs or support information with us directly. But during normal use - generating user stories, indexing your sources, publishing to Jira - there is no data processing on our side.
-
GDPR-compatible architectureYou are data controller and data processor for your own BA Star installation.
-
No telemetry, no usage trackingWe collect nothing. There are no analytics hooks, no crash reporters, no beacon calls back to us.
-
Credentials encrypted at restIntegration credentials (API keys, tokens) are AES-256 encrypted inside your own database. They never leave your server.
-
OIDC / SSO supportIntegrate with Keycloak, Okta, Auth0, or any OpenID Connect provider - using your own identity infrastructure.
Deployment takes less than an hour
We can walk you through every step - from container setup
through tool integration and the first sessions.