Alternative forIdibu
Your applicants expire after twelve months
In Recruitly the database is permanent and the posting is included. From $25 per user, with no minimum term.
idibu terms of service
“idibu will remove all processed data relating to posted jobs and applicants with a default data retention policy of 12 months.”
“Where the Job Board charges its own fee, the Client is responsible for arranging and maintaining access to the Job Board.”
“Invoices paid by credit card (via GoCardless, PayPal, Stripe or any other service) are subject to a 5% processing fee.”
“Following the termination of the contract between idibu and the client, idibu reserves the right to remove all client data after a period of 30 days.”
Clauses quoted verbatim from ww2.idibu.com/terms, 9 August 2026.
A posting tool is not a talent pool
Every agency ends up treating whatever holds the applications as a database it can come back to. That is the whole value of last year’s advert: the eleven people who were nearly right. A twelve-month default retention policy quietly removes exactly that, and you find out when you go looking.
Recruitly keeps them. Search, AI matching and re-engagement campaigns all run over the whole history, because the history is the point.
One system, and it keeps everything
Idibu is a layer that posts jobs out of the CRM you already pay for. Recruitly is the CRM, and the posting is part of it.
The database is permanent
Candidates, applications and the history against them stay until you delete them. There is no retention policy quietly ageing out last year's applicants, because the database is the product rather than a by-product of posting.
Distribution is included
Posting to 50+ boards is part of creating the job, not a separate licence sitting alongside your CRM. You keep your own board contracts and credits — what disappears is the layer in between.
Export whenever, free
Your data is exportable at any time, at no charge, without a termination clock running. We would rather you could leave easily than have to argue about it later.
Start free, no contract
A free plan, then $25 per user per month with no twelve-month commitment and no minimum seat band. One recruiter can start on their own this afternoon.
You are already paying for a CRM
Idibu has no client records, no placements, no timesheets and no invoicing. Their own product page describes managing the posting process from inside your CRM. So the licence is never the whole bill — there is always a Bullhorn, Vincere or Access line beside it, doing the half Idibu does not.
Your CRM licence
Records, placements, invoicing
Idibu licence
Posting and applicant filtering
Job board contracts
Billed by the boards (clause 3.1)
Recruitly
The first two, in one plan
Recruitly vs Idibu
Idibu does distribution well. It is a layer, not a system of record.
| Post to multiple job boards | Included | Yes |
| Applicant tracking system | Included | — |
| Client and contact CRM | Included | — |
| Placements, timesheets and invoicing | Included | — |
| Applicant data retention | Permanent, until you delete it | 12 months by default (clause 7.4) |
| Minimum term | None — monthly | Twelve months |
| Published entry price | $25/user — free plan available | £125/month for five licences |
| Card payment surcharge | None | 5% (clause 11.4) |
| Needs a separate CRM alongside it | No — it is the CRM | Yes |
| Telephony, WhatsApp and e-signature | Included | — |
| AI matching and application review | Included | — |
| Data after you leave | Export any time, free | Removable after 30 days |
Source: ww2.idibu.com/terms and ww2.idibu.com/pricing, 9 August 2026. Bands above five seats are not published, so none is quoted here.
Questions before you move
Can Recruitly replace Idibu for multiposting?
Yes, and it replaces the CRM the Idibu licence sits next to at the same time. Recruitly posts natively to over 50 job boards including Indeed, Reed, CV-Library, Totaljobs and JobServe, with per-board field mapping and scheduling, and applications arrive directly on the job as candidate records. Because posting is part of the system that holds the job, there is no integration between two vendors to configure or debug.
Is it true that applicant data is deleted after twelve months?
That is what their terms say. Clause 7.4 states a default data retention policy of twelve months on processed data relating to posted jobs and applicants. Whether it is enforced on your account is a question for them, and we would encourage you to ask it directly rather than take our reading of it. The reason we raise it is that agencies routinely treat a posting tool as a talent pool, and a twelve-month default is incompatible with that. In Recruitly the database is permanent.
Do I still need my own job board contracts?
Yes, with either product, and that is normal. Idibu's clause 3.1 puts board fees on the client, and Recruitly works the same way: you keep your own rates, credits and relationships and we post using your credentials. What you stop paying for is the middleware, not the boards.
What does Idibu cost?
Their pricing page publishes one figure: five user licences from £125 per month, with a footnote confirming the price is for all five users rather than per user. Bands above five seats are not published. Their FAQ describes twelve-month contracts, with quarterly or monthly billing available as a payment schedule rather than a cancellable term. Ours is on the pricing page: free to start, then $25 per user per month.
Is there anything Idibu does better?
Multiposting is their craft rather than a feature they added, and it shows in the breadth of the board network and the depth of the per-board field mapping, particularly across European boards. If your agency posts to a long tail of regional or niche boards and is happy with the CRM you already run, that focus is a genuine strength and a fair reason to stay. We will tell you honestly during a trial whether the boards you actually buy are covered by us.
How do I move without losing anything?
Start the export before you terminate, because clause 7.4a lets Idibu remove client data thirty days after the contract ends. Take delivery of the file while the account is live, then close it. On our side a migration specialist runs a two-stage process with a sample export on day 1, sign-off on day 5, validation of 100 records per module on day 12 and the full load on day 14, followed by a parallel run before go-live.