Think of Arctype as “phpMyAdmin meets Postman”. Most of our team grew up learning how to program using the LAMP stack and we missed the experience of interacting with our databases using phpMyAdmin. We wanted to bring back the experience of a simple app that lets you explore and query your databases, but with an updated and modernized interface.
At the same time, we were heavily inspired by the ease-of-use and collaboration features of Postman. We wanted to create a super useful, collaborative app like Postman that your whole team uses for development—but for databases instead of APIs.
We have a few thousand developers using Arctype today but we haven’t shared it with the HN community yet–we’re excited to hear your feedback! We also have a very active Discord community at arctype.com/discord where developers can ask questions and talk about databases/SQL.
I’m sure the community has a lot of questions, so we’ve compiled a list of the most common ones we get:
“Why isn’t Arctype open source yet?”
It will be soon! We’ve been focusing mostly on features that users have been asking for, as well as performance, stability, and security. We’re not completely happy yet with the documentation and development experience of contributing to Arctype, but this will be a core focus for us in the coming weeks. We just want to make sure it will be very easy for the community to contribute once we publish on GitHub.
“How does Arctype make money?”
Arctype is free (and will be free forever) for most developers. We have a typical SaaS model for large teams based on a per-seat license as well as an enterprise version that companies can run on their own infrastructure.
“Why is Arctype built using Electron?”
We wanted to make it easy for anyone to use Arctype–Electron is currently the most practical solution to make it cross-platform and also accessible via a web app. Apps like VSCode and Discord have shown that it’s possible to achieve decent performance so we’re confident that over time the advantages of developing on Electron will outweigh the slight performance hit compared to native apps.
“Does Arctype need an account?”
You can use Arctype without an account or you can login via email or Google. Certain features such as sharing queries and dashboards with your team require an account.
“Is Arctype secure / does it store credentials?”
All of your credentials are stored locally, and queries are also executed locally on your machine. We do have a feature that lets you automatically share your credentials to your team, but that is strictly opt-in, and all credentials are encrypted on our backend. Additionally, we have an enterprise version that companies can run on their own infrastructure for organizations that have stringent security requirements. If you’d like to learn more, we have more info at arctype.com/security.
“Does Arctype use any analytics software?”
Arctype has usage-based analytics and error reporting (we use Sentry) that we use to improve the app and to help us fix bugs/crashes. However, this can be turned off. Additionally, Arctype can be used fully offline.
“Why doesn’t Arctype support X database?”
Email me at justin at arctype.com :) We’ll make it happen.
