Resource Pooling
OpenAllow Resources to be deployed/used/shared across multiple locations rather than force all resources to be used in a single location. A good use case is to to have monitoring apps from multiple locations.
Feedback
Suggest apps and features, and vote on other people's ideas. This list is live from the panel — every status change is public.
Posting and voting use your Caliber Node account — creating one is free and takes a minute.
This board is for ideas, not support — if something is broken on your account, open a support ticket instead so we can actually fix it for you.
Allow Resources to be deployed/used/shared across multiple locations rather than force all resources to be used in a single location. A good use case is to to have monitoring apps from multiple locations.
We're looking ahead at potential new locations for our platform, and we want to hear from you. Right now we're considering: - Europe - Canada - Another U.S. location - Asia-Pacific Would an EU location be useful to you? If so, where would you like to see us—Germany, Netherlands, UK, or somewhere else? We're not promising a new location just yet. We simply want to see where the demand is before we make our next move. Where should we deploy next?
Like flyio have grafana dashboard, it have some graph showing useful metrics over time to improve apps: - Number HTTP requests and region where the request come - HTTP response latency, response time average - Infra metric around container (CPU, RAM, Load Average, Volume RW, Volume Size) over time Since CN support bring your own image, I think it nice to have this
Post it on the board — the most-voted ideas genuinely shape what gets built.