Opportunities › Offline database with reliable licensing and support › Proposed app
Keepfile
Local-first database with a license that never phones home
- Score
- 45
- confidence 52
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 1980
- Mature market · AI estimate
ScreensConcept
Desktop app: Users build tables, forms and reports in a database and work with structured data and records—extended focused work. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
License
Works offlineActive
- PlanPerpetual
About this appAI proposal
Keepfile is a table-and-forms database that runs in your browser and stores data on your own device. Build tables, forms and reports and keep working with no connection. Your license is a signed file checked on the device, so it never depends on a server being up.
It is made for businesses that run legacy or mission-critical record keeping on offline databases such as dBase files and cannot afford a lockout. Import your .dbf tables, keep working, and export to open formats whenever you like.
The difference is simple: no periodic call home, no activation server, no lockout. Support runs on email and a status page hosted apart from the product website.
- Tagline
- Your data, your license, your desk. No server required.
- Voice
- SteadyPlainDependable
- Why this name
- Keep says what the product promises: access stays with you. File points to the plain tables and files the audience already works with.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Signed offline license file
Activate once with a file or code. Validation happens on your device, with no recurring check and no lockout if our servers go down.
No member yet
Import .dbf tables
Bring in dBase-style tables with fields and records intact, and check them in a preview before you commit the import.
No member yet
Works fully offline
Tables, forms, queries and reports run from local storage. A connection is only needed for optional updates.
No member yet
Open-format export
Export any table to CSV, JSON or .dbf at any time, so your data is never held hostage by the tool.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F4D3FPine · primary#F4F1E8Paper · surface#1F2A24Ink · text#E0A030Amber · accent#6B8A7ESlate Green · data
Typography
Aa
Keepfile
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Your data, your license, your desk. No server required.
PricingAI proposal
dBase's pricing page (verified) lists 2 paid plans from $399 to $499 one-time. Solo and Office sit near that range; the support add-on has no benchmark in the material and is a starting point to test.
Solo
$349 once
- 1 seat
- Offline license file
- Import and export
- 1 year of updates
Office
$449 once
- Up to 5 seats
- Offline license file
- Forms and reports
- 1 year of updates
Priority support
$29 a month
- Guaranteed email response time
- Status page access
- Migration help
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Keepfile is a single-office tool that works offline, so use creates little exposure to outsiders. Growth comes from content, search, and answers in communities where dBase users discuss licensing problems.
- Do they become customers?
- Reached buyers are the people already looking for a way out of lockouts, so they can pay. What needs testing is whether they will move from dBase files and programs to a new tool.
- First customers
- Small businesses with 1 to 10 staff that keep customer, inventory or order records in dBase .dbf files and have been locked out or worry about it.
- Where to reach them
- Hacker News and forums: Join threads on dBase licensing problems and offer a free .dbf import check to people who ask for an exit path.
- Search content: Publish guides on opening .dbf files offline and moving off license-server software, with a free converter.
- Direct outreach: Contact consultants who maintain legacy dBase systems for small firms and offer them a partner license.
- First milestone
- Ten paying customers from legacy dBase users, each importing real .dbf files, within 60 days of launch.
Why people already pay for this
- Public claimdBase customers are locked out of offline database when copy-protection servers are unavailable, despite being paying customers.
- Public claimdBase company has ongoing licensing and support problems.
- Public claimdBase is an offline database system whose copy-protection periodically calls home to online license servers.
- VerifieddBase's pricing page lists 2 paid plans, from $399 to $499 one-time
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Local storage engineSQLite compiled to WebAssembly with browser file storageGives real offline tables and queries on the device with no server.
- This app · License signingPublic-key signed license filesLets the app verify a license on the device with no server call.
RisksAI inference
- TechnicalBrowser storage can be cleared or limited by the browser, which risks data loss. Reliable local backups and persistent storage requests are needed from day one.
- TechnicalOld .dbf variants, memo files and code pages vary widely. Imports may fail on real customer files, and exact compatibility with dBase programs is hard.
- CommercialCustomers with old dBase code (programs written in its language) may not switch to a table-and-forms tool. Demand beyond data access is unproven.
- CommercialOffline licenses can be copied. Too little protection hurts revenue, and too much brings back the lockout problem the product exists to avoid.
- DataUsers trust the product with mission-critical records, so a bug that corrupts data would end trust quickly.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.