Koyeb
TestingHosting
This connection is being prepared. Usage coverage may be limited by the provider plan and API.
Under investigation
What we are checking
We are preparing usage coverage for Koyeb. Numbers appear only when BeforeRed can read a supported signal with a known limit.
No usage metrics are available for this provider yet.
How to connect
Connection safety
Authorization
Safer access required
The credential currently available to BeforeRed is broader than the monitoring signal requires, so new connections are disabled.
Capability boundary
No credential input is shown and the server rejects direct connection attempts until this boundary is verified.
Not available to connect.
Provider research and runtime wiring can continue without asking users for an overpowered credential.
Capability manifest
What BeforeRed can read
Every capability reflects what BeforeRed can currently read from the provider. Unsupported data stays clearly marked.
Authentication BeforeRed can connect to the provider at all. | Planned |
OAuth OAuth is available, with a documented flow. | Planned |
Account discovery BeforeRed can list the user's account or organization. | Planned |
Project discovery BeforeRed can pick a specific project or service to monitor. | Under verification |
Plan detection BeforeRed can read which plan you are on. | Under verification |
Free-plan support Useful signal is available on the Free / Hobby tier. | Planned |
Usage monitoring Current usage values for the metrics you care about. | Under verification |
Historical usage BeforeRed can read past values, not only current usage. | Under verification |
Limit retrieval BeforeRed can read the currently applicable limit. | Planned |
Cost monitoring Spending can be attributed to specific projects or services. | Under verification |
Token refresh OAuth tokens are refreshed automatically without re-auth. | Planned |
Disconnect The user can revoke access from the provider side and we know. | Planned |
Related