Who writes these articles
Articles are published as INFRO Editorial: The team building INFRO, a BYOK-first control plane for production AI. Articles are written from the engineering work on the gateway and cite their external sources. There are no individual bylines yet. When a named person writes or reviews an article, the article will say so, and a review is never implied where none is recorded.
INFRO sells a software subscription for a control plane in front of the AI provider accounts its customers already hold. It takes no share of model spend. That is a commercial interest in the subjects these articles cover. Where an article discusses INFRO it does so under a heading that names it, and the product section at the end lists the current availability of every capability the article mentions.
How claims are sourced
- Facts about a provider, a standard or another product link to the primary source — the provider's own documentation, a specification, or a published paper — and the source list records when it was last opened.
- Statements about INFRO's behaviour match the public documentation and the capability status published on the site. Anything not yet generally available is labelled.
- Worked examples with numbers are marked as illustrative. We do not publish benchmark results, customer outcomes or savings figures unless the method and data behind them are published alongside.
- General engineering advice is written as advice, not presented as a measured result.
What the dates mean
- Published is when the article first appeared.
- Updated appears only when the content changed in a way a reader would notice, and every update has an entry in the article's revision history saying what changed.
- Last checked is when the article was last reviewed against its sources and the current product. Reviewing an article does not change its updated date unless the text changed.
How often articles are reviewed
Each article declares how quickly its subject goes out of date and must be reviewed at least this often. An article that misses its review by more than 14 days fails the site's content checks until it is reviewed, corrected or withdrawn.
| Subject | Review at least every |
|---|---|
| Pricing and model comparisons | 30 days |
| Provider capabilities | 30 days |
| INFRO product claims | 30 days |
| Security and compliance | 90 days |
| Engineering practice | 180 days |
Corrections
If something in an article is wrong or out of date, email hello@infro.io with the article and the passage. Corrections of substance are recorded in the revision history of the article they change.