Your data stays local, private, and fully in your control. Galaxy is designed from the ground up with a local-first, privacy-preserving architecture — and a deep commitment to modern security best practices.
Our v0.1-alpha is coming in April 2025.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Data Ownership, Control, and Compliance
Galaxy ensures that you maintain full ownership and control over your data while our team builds with security and compliance in mind.
Ownership & Data Privacy
You own your data: Galaxy users retain complete ownership over their inputs and outputs.
No model training on your data: We never use your data or schemas to train any models.
Data remains yours: All content you create, including queries and outputs, remains your intellectual property.
Access Control & Permissions
Your organization controls access — we enforce a strict least privilege model.
Self-Managed Access
Admins can define and manage permissions for database connections, environments, and more.
Minimal Default Permissions
New users start with minimal access by default, ensuring sensitive data is protected out of the box.
How Galaxy Connects to Your Infrastructure
Galaxy runs locally and never transmits your query data to the cloud.
Self-Managed Access
Desktop app only: Galaxy runs as a desktop app; no queries are routed through our servers.
No data leaves your system: Query execution and results remain inside your infrastructure.
Galaxy AI & Schema Handling
AI is optional and disabled by default.
If enabled, only schema metadata (e.g., table names, column names) is shared — never raw data.
No AI training on your schemas, and schema details are not stored after the session.
Chat History & Auditing
Chat history is scoped to your org and workspace.
Audit logs help admins monitor usage and ensure compliance.
Encryption & Data Protection
We follow industry standards to protect your credentials and usage data.
TLS 1.2+ encryption in transit
Encrypted credential storage (locally, if enabled)
We do not store query history or user data on our servers