Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
File4Base is an open-source project aiming to bring the visual database-building workflow of classic desktop tools to a modern, self-hostable application. Its author describes a canvas for forms, lists, reports, and queries, alongside relational data in PostgreSQL and a step-based scripting workspace. The project is still in development: its author reports that foundational specifications are complete while key backend and layout-rendering components remain in progress.
What File4Base is intended to do
File4Base is presented by its author, Mario Ezquerro, as an open-source database and layout editor for people accustomed to classic desktop database builders. The intended workflow combines a visual editor for building interfaces and reports with ordinary relational database structures. The project aims to support forms, lists, reports, queries, and a step-based scripting workspace. These are stated goals, not evidence of completed feature parity with any established database product.
The practical premise is to pair a visual application-building workflow with access to familiar database tables and columns. The project positions that approach as a way to reduce dependence on a proprietary file format; however, its “zero lock-in” language is a project claim, not a guarantee. The concrete basis described is standard SQL and a self-hostable database architecture. Read the project author’s article.
How the architecture is described
The project’s article names Flutter for the desktop client, Go for the backend, and PostgreSQL 16 for data storage, communicating through REST and WebSocket interfaces. The public repository describes a decoupled Go backend and Flutter frontend and documents PostgreSQL 16 and MariaDB options for server persistence. It also describes Docker Compose deployment, a browser-accessible client in server mode, and standalone macOS, Windows, and Linux desktop clients. These are documented design and execution paths, not independently verified installation results.
#1 Best Overall
- Client: Flutter, with desktop clients and a browser-accessible client described in server mode.
- Backend: Go, described as decoupled from the client.
- Persistence: PostgreSQL 16 in the project article; the repository also documents MariaDB as an option for server persistence.
- Communication and deployment: REST and WebSocket are named in the article; Docker Compose is documented by the project.
The intended separation between interface, backend, and database matters because the project is not simply a desktop file that contains both an application and its data. Its stated design uses a service backend and conventional relational databases, with deployment choices documented in the repository. The details do not establish production reliability, security suitability, or that all components work equally across environments.
What Antigravity contributes—and what it does not establish
Ezquerro says the team uses Google Antigravity with architectural blueprints, JSON schemas, and roadmap documents while developing Go and Flutter modules. Google describes Antigravity as an agentic development platform and lists an IDE, CLI, and SDK. Google Antigravity is part of the development workflow reported by the author; its use does not independently validate File4Base or demonstrate a measurable improvement in development speed or software quality.
Development status and maturity
In the September 24, 2026 project article, the author marks the monorepo and Dockerized development environment, a FileMaker feature reference, and three-panel Script Workspace specifications and mockups as complete. The same checklist marks the backend metadata catalog and dynamic JSON layout renderer as in progress. This is the author’s status report at publication, not an independent audit of the codebase.
The repository documents server and desktop modes and provides build commands, but documentation alone does not show that a build will succeed on a particular machine or that the software is ready for production use. The reported in-progress components are especially relevant to anyone considering File4Base for real work: the metadata catalog and renderer are central to the promised relationship between database structure and dynamic visual layouts.
Rank #3
How to assess whether it fits your needs
File4Base is best understood as a project to watch or evaluate experimentally, rather than as a proven replacement for FileMaker, Access, or 4D. If you are comparing it with a tool you already use, evaluate the capabilities that affect your workflow directly:
- Data access and portability: Confirm which database your intended deployment uses and whether your applications can work with the tables and SQL access you require.
- Implemented features: Check the actual state of layouts, reports, queries, and scripting rather than relying on the project’s intended feature set.
- Deployment and maintenance: Decide whether you can operate a self-hosted backend and maintain its database, updates, backups, and availability.
- Maturity and support: Establish what release or support expectations apply before putting important workflows on an early-stage project.
- Migration effort: Map your existing data, scripts, forms, and reports; the available sources do not establish a migration path or provide migration test results.
- Licensing: Review the repository’s current license and its terms for your intended use rather than inferring rights from the open-source label alone.
Where to follow the project
The public File4Base GitHub repository is the place to examine the README, documented execution modes, build commands, and project license. For the author’s explanation of goals, development workflow, and reported checklist status, see Mario Ezquerro’s project article. The author invites readers to share what they miss most from classic desktop database builders: “Let us know in the comments: what is the single most critical feature you miss from classic desktop database builders?”
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
