File storage
Each project keeps its own files, public or private. A public file gets a stable URL you can drop straight into an image tag.
Utility backend for builders
Build the product, not the plumbing.
Day one of your new app, the sign-up pages again: file storage, an email sender, short links, QR codes, PDFs, each with its own key and its own dashboard. FilesHub puts that plumbing on one shelf. One key covers it.
Beside your backend
Your main backend keeps the product logic. FilesHub holds the utilities beside it. That's the fifth dashboard you don't have to open.
Behind one key
Each key is scoped by permission and by allowed origin. Storage, email and the small tools all answer to it.
Why it exists
Built to run its maker's own apps, and it still does.
Your project sits on the same shelf. Access is by request, and every service's monthly price is written down in /pricing.md.
On the shelf
Three things most apps need, and one to ask for.
Transactional email
Email goes out from FilesHub's sending domains, with templates, schedules and delivery logs of what went out, and the sender name is yours to set on each send.
Small tools
Short links, QR codes, a paste bin, PDFs, one-time codes and webhooks are the jobs you'd otherwise rebuild for every app, and 50+ utility endpoints are listed in /docs.
Project Vault
One encrypted place per project for its credentials and config files. Values are withheld until someone reveals one, and each reveal is recorded. It's off by default: ask for it.
Projects kept apart
Each project has its own storage and API key.
Scoped keys
Permissions decide what a key may call. Allowed origins decide where it's called from.
Specs for AI agents
An integration spec your coding agent can read, in JSON and Markdown.
REST docs and Postman
Try a request from the Postman collection before you write any code.
Searchable sitemap
Every public page in one list, plus an RSS feed for new posts.
Policies you can find
Privacy, terms, cookie, GDPR and contact pages, plus how to delete your data or account.
How It Works
What happens between asking and shipping.
01
Request access
Approval comes before any project or key.
02
Your project, your key
Once approved, each app gets its own project and an API key.
03
Wire it in
Follow the docs, or hand your coding agent the AI spec. Your main backend keeps its job.
04
Ask for more
Higher quotas, or the project vault, when a project needs them.
For coding agents
The API, described for machines.
Your coding agent gets its own page at /ai-integration, in JSON and Markdown. Pair it with the Postman collection, and you can check your agent's first request by hand.
Sitemap and feed
Looking for a page? The sitemap lists every one.
Docs, policies and blog posts sit in one list you can search. New posts also reach the RSS feed. Crawlers get both as XML.
FAQ
Questions to settle before you request access.
What is FilesHub?
FilesHub is a utility backend that sits beside your own backend. Each project gets file storage, transactional email and 50+ utility endpoints behind one API key, and a project vault on request.
What does one API key get me?
One key gets a project its file storage, its transactional email and the small utility endpoints, from short links and QR codes to PDFs and webhooks. The key is scoped by permission and by allowed origin. The tools are listed in /docs.
How much does FilesHub cost?
Each service has its own monthly price, and a project pays only for the services it uses: file storage, email, email marketing and each developer API. The full list is on /pricing, and as Markdown at /pricing.md. Access is by request.
Does FilesHub work with AI coding agents?
Yes. The /ai-integration page publishes FilesHub's specs as machine-readable JSON and Markdown for coding agents. Give your agent the link, and it can work from the spec alongside the REST docs.
Can I delete my data?
Yes. Files can be deleted with your project's API key at any time, and for the rest of your data, or the account itself, the steps are at /data-deletion and /account-deletion.