At Basedash, we are users of our own product.
Our product, Basedash, has the following architecture, fairly typical for a web app:
And what does our product do? It facilitates database management.
Recall, we ourselves have a database to manage (see item 3 above). So, naturally, we use Basedash to manage Basedash.
Basedash connects to our customers’ databases allowing our customers (teams of technical and non-technical users) to read and write to their own databases with a high quality user interface with thoughtful collaboration and access controls.
And we ourselves are one of our own customers. Those connections, those affordances for reading and writing to one’s own database, are themselves backed by tables and records in our production database (item 3 above).
For example, our production database has certain tables along the lines of “user”, “workspace”, “database”, “schema”, “table”, “column”, and “edit” (paraphrased), in order to keep track of users’ own transactions with their own databases.
Imagine we have a customer that reaches out to us for support. We’d like to pull up that “user” record, to see things like what plan they’re on, what workspaces they are a member of, what databases they’ve connected in order to manage them with Basedash.
Doing things the manual way would look something like this, a developer querying the database with the command-line interface:
But it’s not always preferable to do things the manual way. Many people use a database administration tool like Postico, or TablePlus to make this kind of thing more approachable and convenient. But we like to use the very database administration tool we are building. So, here’s how we might look up a user in Basedash, by simply searching for that user’s email in our “user” table:
This situation of being one’s own customer is known in the industry as “dogfooding”, or “eating your own dogfood”, and it’s something we embrace. We’re using Basedash for Basedash at Basedash.
Get to know what Basedash can do and how it changes traditional internal tools.
See a full app that connects to a Postgres database and external API made from scratch.
Ship your product faster.
Worry about internal tools less.
No credit card required.
September 26, 2022
Sooner or later in development work, there comes a time where you just need a flowchart. Recently we started using Mermaid, a markdown syntax supported by Notion and Github to document and share and annotate new features in-line rather than having to use a design tool or draw them out by hand.
September 21, 2022
Doing user research is difficult in and of itself, but no matter how good your are at asking the right questions, gathering data, taking insights from research, and putting that data to use, one of the most important parts of user research is finding the right users to talk to in the first place.
September 14, 2022
Product analytics tools are failing startups. At an early stage (pre-product-market fit), aggregate data is a distraction.The cure? Entity-level data.
September 1, 2022
Internal tools take time, resources, effort, and often get very little resources to build, and less to improve and grow over time. Learn how our designer, Tom Johnson, has seen and felt the pain of building internal tools over his career and how Basedash solves those issues.
August 29, 2022
Internal tool product management is identifying a need for, creating, and managing internal tools that will fulfill the needs of multiple people at your company. It's one of the most intimidating product roles in tech startups, but it doesn’t need to be.