Opportunities › Rapid backend generation from relational databases › Proposed app
Spigot
Instant REST and MCP APIs with access rules for PostgreSQL and MySQL
- Score
- 47
- confidence 57
- Evidence
- 7
- items on the page
- Rivals
- 3
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2012
- Mature market · AI estimate
ScreensConcept
Desktop app: Backend developers connect databases, build custom routes, set access rules, and monitor request logs through dense configuration interfaces. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Connected
Schema synced14 routes
About this appAI proposal
Spigot reads your PostgreSQL or MySQL schema and gives you a working REST API and an MCP endpoint for AI tools. Tables get CRUD routes, and you can add your own SQL as named routes. No backend boilerplate to write or keep up.
Access is set per role, per table and per column, in one screen. Sign-in, API keys and request logs come with it. Run it hosted, or self-host it next to your database.
It is for small teams who have a database and a frontend but no wish to maintain a server in between. Every rule is shown as readable policy, so you can check what each role can reach before you ship.
- Tagline
- Point it at your database. Get a secure API.
- Voice
- PlainPreciseCalm
- Why this name
- A spigot turns a stored supply into a flow on demand, as Spigot turns tables into endpoints. It is short, plain and easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
API from schema in minutes
Connect PostgreSQL or MySQL and get REST routes with filtering, paging and CRUD for every table. No code generation step.
No member yet
MCP endpoint included
Expose chosen tables and saved queries to AI assistants over MCP, with the same roles and limits as the REST API.
No member yet
Custom SQL routes
Save a parameterised query as a named route with typed inputs. Version it and roll it back.
No member yet
Role and column access rules
Set who can read or write each table and column. A preview shows exactly what a role sees before you publish.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C4ADeep Teal · primary#F6F3ECPaper · surface#1B2422Ink · text#E3A02BSignal Amber · accent#5E8C61Moss · data
Typography
Aa
Spigot
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Point it at your database. Get a secure API.
PricingAI proposal
Based on the Supabase page (free, then $25 to $599 a month) and the Hasura page (free, then $5 to $30 by usage), both verified. Tiers here are a starting point to test.
Free
Free
- 1 database connection
- Hosted REST and MCP
- Basic roles
- Community support
Team
$29 a month
- 5 database connections
- Column-level access rules
- Request log, 30 days
- Custom SQL routes
- Email support
Scale
$149 a month
- 25 connections
- Higher rate limits
- Request log, 1 year
- Schema change alerts
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. Spigot sits behind the customer's own apps and MCP clients, and end users do not see it. Growth comes from developer content, open docs and word of mouth among developers, not from a loop inside the product.
- Do they become customers?
- Not a loop. We would need to test whether developers who find it through search and tutorials move from the free tier to a paid plan, and whether self-host users ask for hosted.
- First customers
- Freelance and agency developers with 2 to 10 people who build client apps on PostgreSQL and want a secure API without writing a server.
- Where to reach them
- GitHub and open-source forums: Answer questions from people comparing instant-API tools and publish schema-to-API walkthroughs with sample databases.
- Developer newsletters and Reddit: Share a short guide on exposing a database to an AI assistant safely over MCP, with a free account link.
- Direct outreach to agencies: Offer a free migration of one existing client backend to Spigot in exchange for feedback.
- First milestone
- Ten paying teams on the Team plan within 90 days, each running at least one production API.
Why people already pay for this
- VerifiedGitHub repository gained 4623 stars in 3609 days
- Public claimPRESTd generates instant REST and MCP APIs directly from PostgreSQL and MySQL databases with CRUD operations, custom SQL routes, authentication and access control without requiring custom backend code.
- Public claimThe platform is low-code, real-time capable, and high-performance, designed for rapid backend development.
- Public claimPRESTd supports both PostgreSQL and MySQL including MySQL 8, with native MySQL support added in version 2.5.
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 · API runtimeLong-running Node or Go service with connection poolingServerless functions on Vercel handle pooled database connections and streaming poorly; the proxy needs a persistent process.
- This app · Secrets storageManaged key vault with envelope encryptionCustomer database credentials must be encrypted and rotated apart from the app database.
RisksAI inference
- CommercialSupabase and Hasura already offer instant APIs with free plans, and open-source tools like PRESTd are free. Spigot must win on simpler access rules and MCP, or buyers will not pay.
- TechnicalGenerated APIs over customer databases can allow slow or heavy queries. Query cost limits, pooling and safe SQL parameter handling are hard to get right on both PostgreSQL and MySQL.
- DataHolding database credentials makes Spigot a high-value target. A breach would be severe for customers, so secrets storage and audits are needed from day one.
- AIExposing databases to AI assistants over MCP can leak data or run harmful writes if rules are wrong. Read-only defaults and clear previews are needed.
- PlatformCustomers' databases must be reachable from the hosted service. Many sit behind private networks, which may push buyers toward self-hosting and raise support cost.
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.