Evidence boundary: The public repository documents an extensible social-media application and exposes integration code and configuration. This page describes only what a reader can verify in that source; it is not a claim about the hosted service's private production deployment.
Documented integration pattern
- Review the repository's environment and integration documentation.
- Identify only provider clients visible in public source.
- Pin package and API versions before reproducing an integration.
- Validate data handling and platform terms for your own deployment.
Relevant provider records
- OpenAI API · official channel
First-party evidence
- Postiz public repositoryFirst-party public source and documentation.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove Postiz's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.