Enterprise

This page states what exists today. FlowFinds was built for one operator running their own inventory, and several things a large organisation expects are not built yet. Where that is the case it is said plainly rather than described as available.

What exists today

• An account per person, keyed to an email address. Sign-in is an emailed single-use link. A cleared cookie does not create a second identity or a second allowance.
• Volume through the usage ladder. The Max tiers run at five and twenty times the reference allowance, metered per feature so one team’s heavy use of the website editor does not exhaust the find engine. See pricing.
• Multiple products under one account. Claims accumulate; each carries its own store, offer, ad artefact and activity, and the dashboard resolves the verdict per product.
• Exclusive inventory that holds across accounts. One product, one founder, enforced in the database. That guarantee is what makes the inventory worth anything at volume, and it does not weaken as accounts multiply.
• The API. Everything the surfaces do is available over HTTP, so operations can be scripted rather than clicked. Start with the API reference and authentication.
• Published measurement. The benchmark, the rubric and every recorded run are public, including the failures, so an evaluation does not have to rest on our description of the product. See research and reproduce our results.

What is not built yet

There is no single sign-on, no shared workspace with roles and permissions, no organisation-level billing across seats, no audit export, and no contractual service level beyond our published availability commitment. We hold no security certification. None of these are on this page as forthcoming features with dates, because we do not have dates for them.

If your organisation needs any of them, that is a conversation rather than a signup. Tell us what you need and we will tell you honestly whether we can serve it now.

Diligence material that does exist

• Product security — tenant isolation, credential handling and the limits on agent authority.
• Data handling and retention — what is stored, for how long, and where.
• Sub-processors — every third party that processes customer data for us.
• Commercial terms and the data processing addendum.
• Supported countries.

Talk to us

Write to [email protected], or use contact to reach the right desk. Security questions go to [email protected].