File4Base is an open-source project aiming to bring the visual, rapid-application-development workflow of classic desktop database builders to a self-hostable system built around relational databases. Its author describes a visual editor for forms, lists, reports, and queries, alongside a scripting workspace; the project is still in development, and its documentation does not establish feature parity, production readiness, or successful operation in every environment.
What File4Base is intended to do
Project author Mario Ezquerro presents File4Base as an open-source database and layout editor for people familiar with classic desktop database tools. The intended workflow combines a visual canvas for designing interfaces and reports with relational data stored in ordinary database structures. The project also aims to provide a step-based workspace for scripting and a backend users can host themselves. These are stated goals, not independently verified capabilities across a finished product.
As an Amazon Associate I earn from qualifying purchases.
The project’s framing is useful if you are considering whether this kind of tool might suit your work: it aims to connect visual application-building with direct access to relational data, rather than make the database itself an opaque proprietary store. The author characterizes this as avoiding lock-in, but that should be understood as project positioning, not a guarantee. Actual portability depends on what the software implements, how an application uses the database, and the effort required to move its layouts and scripts.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow the project says it is built
Ezquerro’s September 24, 2026 article names Flutter for the client, Go for the backend, PostgreSQL 16 for the database, and REST and WebSocket communication between components. The public repository describes a decoupled Go backend and Flutter desktop frontend, documents PostgreSQL 16 and MariaDB options for server persistence, and provides Docker Compose deployment instructions.
#1 Best Overall
| Area | What the project documentation describes |
|---|---|
| Desktop client | Standalone clients for macOS, Windows, and Linux, according to the repository README. |
| Server mode | A Docker Compose deployment path and a browser-accessible client described in the repository README. |
| Data persistence | PostgreSQL 16 is named in the author’s article; the repository README also documents MariaDB as an option for server persistence. |
| Communication | REST and WebSocket communication are described in the author’s article. |
These details describe documented architecture and execution paths. They are not installation test results: the documentation alone cannot confirm compatibility with a particular machine, deployment configuration, or workload.
What Antigravity has to do with File4Base
Ezquerro says the team uses Google Antigravity during development, working from architectural blueprints, JSON schemas, and roadmap documents to build Go and Flutter modules. Google describes Antigravity as an agentic development platform and lists an IDE, CLI, and SDK. The available descriptions support saying that the project author reports using the platform; they do not show that Antigravity independently tested File4Base or produced a measurable improvement in speed or quality.
What is complete—and what remains in progress
In the project article’s checklist, the author marks the monorepo and Dockerized development environment, a FileMaker feature reference, and three-panel Script Workspace specifications and mockups as complete. The backend metadata catalog and dynamic JSON layout renderer are marked in progress. This is the author’s status report in that article, not an independent audit of every module or a guarantee that listed work has shipped in a usable release.
Free tools Windows power users keep installed
One-click scans. No signup required.
The distinction matters when evaluating the project. A completed specification or mockup is not the same as an implemented feature, and a documented build or deployment route does not establish release quality, security suitability, production support, or equivalence with an established database builder. The available status information supports treating File4Base as an early-stage project in development.
Rank #3
How to evaluate it for your own work
There is not enough evidence in the project descriptions to recommend a particular File4Base configuration or claim that it can replace another tool. If you are assessing whether to follow the project or eventually try it, compare what is actually implemented with your current workflow:
- Data portability: Check which database structures and export paths are available, and whether your applications can work with the underlying data independently.
- Deployment: Compare the documented server and desktop models with your operating systems, hosting constraints, and maintenance capacity.
- Layouts and scripting: Verify that the forms, reports, queries, and scripting features you rely on exist in working software, not only in plans or mockups.
- Maturity and support: Look for release history, issue handling, security practices, and a clear support model before relying on it for important work.
- Migration effort: Plan for the possibility that layouts, scripts, and application behavior will need to be rebuilt; no migration test or complete feature comparison is established in the project materials described here.
- Licensing and upkeep: Review the repository’s license and decide who will maintain the application and its database deployment over time.
Project sources and contribution context
The project author’s article, “Building File4Base: The Modern, Open-Source Alternative to old file bases (Powered by Antigravity)”, was published September 24, 2026 and describes the goals, development approach, and progress checklist. The File4Base public repository documents the project architecture and execution paths. Google’s Antigravity product page describes the development platform. Read those materials as project and vendor descriptions, not as independent validation of File4Base’s performance or readiness.
Ezquerro closes his article with a question for readers of 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.
