floe-guard
UNCLAIMEDfloe-guard — The spend meter, cost/margin, & budget gate for AI voice agents. Meters STT + TTS + LLM + telephony per call, out of the box (Pipecat, LiveKit — Python & TypeScript). Hard-stops the next turn before i. Listed under Cost and usage tracking in the Observability / Evals layer. 1 of 6 comparison attributes are recorded, each with the page it was read from.
Bill and get paid per verified AI outcome. Floe reconciles the AI tasks / outcomes you bill against your customer
4 OF 4 SIGNALS HELD
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for floe-guard.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From floe-guard? No claim is needed for this: a link to your docs that names what floe-guard runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
1 answered · 5 unanswered6 questions declared by Cost and usage tracking. Most rows across the directory read like these.
“Tag every AI cost to the task, the person, the team, the P&L line.”2026-10-06
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
8 products in Cost and usage tracking. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY
Frequently asked
Is floe-guard open source?
What does a blank mean on the floe-guard page?
Where do the floe-guard figures come from?
Can floe-guard change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by floe-guard?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “floe-guard — Cost and usage tracking”, read 6 October 2026. Cost attribution: task, the person, the team, the P&L line as published at floefinance.com. https://www.infratoapp.com/products/floe-guard
What floe-guard can and cannot change here
Claiming the organisation lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.