// the find
wannabespace/conar
AI-powered tool for working with Postgres, MySQL, MSSQL and Clickhouse.
Conar, which its README brands as Tamery, is an Electron desktop client for PostgreSQL, MySQL, MSSQL and ClickHouse, with an AI assistant for writing and optimizing SQL. Connection strings are stored in a hosted backend (Hono, oRPC, Drizzle) rather than only on the local machine, and that is the main design decision to weigh before using it. It suits developers who work across several engines and are comfortable with a cloud-backed client.
- Schema codegen is a real feature here: apps/app/src/core/codegen/formats emits Drizzle, Kysely, Prisma, Zod and plain SQL from a schema, with a sql.test.ts covering the SQL output. Most database clients stop at a DDL dump.
- Dialect logic is split by object kind (constraints, enums, functions, indexes, policies), each with list, create, drop, recreate and alter modules, and a capabilities file sits in core/catalog. That layout is the right shape for four engines, and shape.test.ts covers the shape logic for constraints and functions.
- Tests exist at more than one layer: colocated unit tests (utils.test.ts, proxy.test.ts, sql.test.ts) and Playwright E2E for sign-up and sign-out against a dedicated test server. The conventions are written down in .agents/rules, so contributors and coding agents read the same rules.
- Credentials leave the machine by default. The README says connection strings are stored in the vendor's cloud and encrypted, but it does not say where the key lives or who can decrypt them. The dev table also lists a Proxy service and the README never says whether query traffic goes through hosted infrastructure.
- The AI section is three bullets. It does not say what the assistant receives (schema only, sample rows, result sets) or whether any of that goes to the model provider unredacted. For a tool pointed at production databases, that is the first thing to document.
- The name and the repo disagree. The repo is wannabespace/conar, but the README is branded Tamery.app with Tamery logos, download links and a local dev domain scheme under tamery.app. Someone arriving here cannot tell which product this is, and the local setup assumes portless and those domains.
- Running it means running most of a SaaS stack: Postgres and Redis (Docker or hosted), then Railway, Stripe, Resend, PostHog and ToDesktop. The README does not say which parts a self-hoster can leave out, so the open-source claim is hard to test without the hosted services.