About Glider

A simple tool for a common problem.

Why Glider?

Getting data from flat files into a PostgreSQL database usually means writing one-off scripts, wrestling with type mismatches, and manually building schema definitions. Glider handles all of that in a visual desktop app — drag in your files, review the inferred schema, and export clean SQL.

Glider was built for data engineers, database administrators, and developers who work with PostgreSQL and regularly need to load data from files. It is especially useful for teams working with NEON PostgreSQL, though it works with any PostgreSQL-compatible database.

Current Status

Glider is currently in beta and is available for macOS. It is under active development. If you encounter issues or have feature requests, please open an issue on GitHub.

Technology

Glider is built with Tauri v2, combining a Rust backend for fast, memory-safe file parsing and SQL generation with a React + TypeScript frontend. The entire application runs locally — no server component is required.

• Backend: Rust with Tokio, streaming file parsers, and tokio-postgres
• Frontend: React 19, TypeScript, Zustand, CodeMirror
• Build: Vite + Tauri CLI

Open Source

Glider is released under the MIT License. The source code is available on GitHub. Contributions are welcome — see the contributing guide to get started.

Glider includes third-party libraries and packages that are subject to their own license terms. While the majority are MIT or Apache-2.0 licensed, some components use other permissive or copyleft licenses such as MPL-2.0, BSD, and Unicode-3.0. See the Third-Party Notices page for a full summary.

Security

Security is a core design principle. Glider processes all data locally, enforces TLS for any database connections, zeroizes sensitive data from memory, and runs with a strict content security policy. For details, see the security policy.