Pricing
A pilot first, then a price per client connection
FileFeed takes the files your clients send over SFTP or email, maps them to your schema once per client, checks every row, and delivers clean JSON to your API. You start with a paid pilot: your first client feed live within 30 days for $3,000, or your money back. After that it is $90 per client connection per month, billed annually, with every new client feed set up by us. No per row pricing. The embeddable importer is free forever.
Starter
Free foreverFree file check and the embeddable importer
Send us one real client file. You get it back mapped to your schema with an error report within 48 hours, no account needed. The embeddable importer is free with unlimited end users.
Feed Pilot
Start hereFor platforms whose clients send files on a schedule
First feed live in 30 days, or your money back
We set up your first client feed and run it live within 30 days. If it is not live, you get the money back.
Feeds
After the pilot, as clients keep coming
Billed annually, minimum 5. $60 per connection from 21 to 50
Every new client feed is set up by us within 5 business days of the file arriving. You pay per client connection, nothing per row.
Why a pilot first
Comparable products sell recurring feeds through a sales process with no public price and a 60 to 90 day implementation. FileFeed publishes the price, starts with one feed, and refunds the pilot if it is not live in 30 days.
Enterprise
More than 50 connections, SSO, audit logs, IP allowlists, a DPA, dedicated or self hosted infrastructure, invoice with net 30. Priced on request.
FAQ
Frequently asked questions
How is FileFeed priced?
A $3,000 Feed Pilot puts your first client feed live within 30 days, or your money back. After that it is $90 per client connection per month for the first 20 connections and $60 per connection from 21 to 50, billed annually, minimum 5 connections, with every new client feed set up by us and no per row pricing. The embeddable importer is free forever, and Enterprise covers more than 50 connections, priced on request.
What is in the Feed Pilot?
Up to 3 sender connections (hosted SFTP, the client's own SFTP server, or an email inbox per sender), mapping confirmed on the client's real files, validation rules, delivery to your API or SFTP as clean JSON, an error report back to the sender, 30 days of monitored runs, and a one page runbook. We agree a written success criterion before you pay.
What happens if the feed is not live in 30 days?
You get the $3,000 back, no questions asked. You keep the mapping work and the runbook.
What counts as a client connection?
One connection is one sender: a client's hosted SFTP folder, a connection to their own SFTP server, or their inbound email address. A connection can feed several pipelines. You pay $90 per month for each one, nothing per row.
Why is there a minimum of 5 connections?
Every new client feed is set up by us, with the client on the call when needed. That is a service, and it needs a steady stream of clients to be worth running for both sides. Five connections is $5,400 per year, a fraction of one implementation hire.
Can I pay monthly?
No. Feeds is billed annually. The pilot is the low commitment step: one payment, one feed, and your money back if it is not live in 30 days.
What is the free file check?
Send us one real client file and get it back mapped, with an error report, within 48 hours. No account needed. A header plus a few rows is enough, and the result comes back as a private link with the mapping, the transforms it needed and the rows that would fail.
Can FileFeed take files by email as well as SFTP?
Yes. Each connection gets its own inbox address with a sender allow list. Clients send the file as an attachment, FileFeed picks it up and runs the same mapping, validation and delivery as a file dropped on SFTP.
What happens when a client file has a bad row?
The row is flagged with the reason it failed. Clean rows go through to your API, and the run shows every error so you or the client can fix the file and reprocess it.
How is this different from an embeddable CSV importer?
An embeddable importer handles one upload inside your app, done by the end user. FileFeed handles files that keep arriving over SFTP or email: each client is mapped once, every file runs through the same validation, and clean JSON is delivered to your API.
What happens when I pass 50 connections?
We tell you before you get there and agree an Enterprise price for the next block of connections. Nothing stops running.
What payment methods do you accept?
The pilot and Feeds are invoiced, and we accept card payments too. Enterprise customers pay by invoice with net 30 terms.
Not sure which step is yours?
Send us one real client file and we will tell you what the feed needs. If clients already send files on a schedule, the pilot is the place to start.