conar
Tamery is an open-source, AI-assisted database management tool supporting PostgreSQL, MySQL, MSSQL, and Clickhouse. It provides a desktop application (built on Electron) and cloud backend for securely storing database connections and generating/optimizing SQL queries via AI models.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | wannabespace/conar |
| Owner | wannabespace |
| Primary language | TypeScript |
| License | AGPL-3.0 — OSI-approved |
| Stars | 1.4k |
| Forks | 108 |
| Open issues | 44 |
| Latest release | v0.32.0 (2026-06-26) |
| Last updated | 2026-07-01 |
| Source | https://github.com/wannabespace/conar |
What conar is
TypeScript/React desktop app with Electron frontend, Hono/oRPC backend, Drizzle ORM for schema management, and pluggable AI SDK integration (Anthropic, OpenAI, Gemini, XAI). Uses Better Auth for authentication, Railway for hosting, and Turbo monorepo structure.
Get the conar source
Clone the repository and explore it locally.
git clone https://github.com/wannabespace/conar.gitcd conar# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires database driver setup for each supported database (PostgreSQL, MySQL, MSSQL, Clickhouse) and connectivity testing before secure connection storage.
- AI model selection (Anthropic, OpenAI, Gemini, XAI) must be configured; API keys managed securely and cost implications understood for query volume.
- Electron desktop app distribution requires platform-specific builds (macOS, Windows, Linux) and auto-update infrastructure; verify ToDesktop deployment pipeline for your target OS.
- Cloud storage of encrypted connection strings assumes trust in Railway infrastructure; audit encryption method and key management before storing production credentials.
- Turbo monorepo structure and Bun package manager add build tooling complexity; teams must ensure pnpm/Bun compatibility in CI/CD pipelines.
When to avoid it — and what to weigh
- Proprietary Database Dependency — If your primary databases are Oracle, PostgreSQL-only variants, or specialized data warehouses not listed (Redshift, Snowflake, BigQuery), support is not yet available.
- Air-Gapped / On-Premise Only — Tamery ships with cloud backend (Railway-hosted) for connection storage. If your org prohibits any cloud-based component or requires full on-premise deployment, this is not suitable.
- AGPL Licensing Constraints — AGPL-3.0 requires derivative works and network-accessible modifications to disclose source code. If you plan proprietary modifications or SaaS redistribution, legal review is required before adoption.
- Immature/Pre-Release Stability Needs — Project created November 2024 with v0.32.0 release. No stable 1.0+ release, no published uptime SLAs, and limited production deployment evidence. Not recommended for mission-critical workflows without vendor support.
License & commercial use
Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license requiring that any modifications, distributions, or network-accessible services built on this code must provide source code access to users. It is not a permissive OSI license.
AGPL-3.0 permits commercial use of unmodified Tamery, but any proprietary extensions, SaaS offerings based on this codebase, or network-exposed derivative works trigger source disclosure obligations. Before commercial deployment (especially SaaS), consult legal counsel on compliance. Using Tamery as-is in a proprietary product is lower risk; modifying and redistributing it is high risk without legal review.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
Project claims encrypted connection strings and password protection in README, but encryption method, key derivation, and storage backend not publicly detailed—requires code audit. Electron desktop app expands attack surface (local execution); verify auto-update signing and dependency vulnerabilities. Cloud-based connection storage (Railway) centralizes credential risk; confirm encryption in transit (TLS) and at rest. Telemetry (PostHog) and billing (Stripe) integrations present; review what data is collected and retention policies. AGPL copyleft license implies source transparency but does not guarantee security; independent assessment recommended before production use with sensitive databases.
Alternatives to consider
DBeaver
Mature, multi-database client with similar SQL assistance (via plugins), broader DB support, and dual open-source/commercial licensing. More stable for production use but lacks AI-first design.
Dataedo
Commercial tool for database documentation, query building, and AI-assisted SQL. Proprietary but established SLAs, no AGPL constraints, and stronger enterprise support.
SQL Server Management Studio (SSMS) / pgAdmin
Native, purpose-built clients for MSSQL and PostgreSQL respectively. Free, mature, no licensing concerns, but no AI assistance or unified multi-DB interface.
Build on conar with DEV.co software developers
Review the AGPL-3.0 license implications with your legal team, audit the encryption and deployment model, and run a POC in non-production. Contact our team if you need guidance on integration or need a mature alternative.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
conar FAQ
Can I use Tamery in a commercial SaaS product?
Does Tamery require internet connectivity?
What AI models are supported?
Is there a managed SaaS version?
Custom software development services
Adopting conar is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.
Ready to Evaluate Tamery for Your Team?
Review the AGPL-3.0 license implications with your legal team, audit the encryption and deployment model, and run a POC in non-production. Contact our team if you need guidance on integration or need a mature alternative.