Feature Requests

Problem: The Envoy gateway intercepts CORS preflight (OPTIONS) requests and returns wildcard headers ( Access-Control-Allow-Origin: * ) before they reach our FastAPI application. This breaks credentialed requests because browsers reject Access-Control-Allow-Origin: * when credentials: 'include' is used. This is per the CORS specification. Current behavior: - Browser sends OPTIONS preflight with Access-Control-Request-Headers - Gateway intercepts and returns Access-Control-Allow-Origin: * - Browser blocks the actual request because wildcards can't be used with credentials Expected behavior: - OPTIONS requests should pass through to the application - Application returns specific origin: Access-Control-Allow-Origin: https://mydomain.com - Browser allows the credentialed request Use case: We have a SaaS application with a custom domain. Our frontend (on a different domain) makes authenticated API calls with cookies/credentials. Without proper CORS handling, our custom domain is unusable for production. Suggested solutions (any would work): 1. Option to disable gateway-level CORS handling entirely 2. Option to pass-through OPTIONS requests to the application 3. Configuration to specify allowed origins at the gateway level This is blocking our production deployment on a custom domain.

Many a time Ctrl+C sigint does not terminate a container. We must be able to manually shutdown container by id. Basically expose main docker commands like docker ps docker stop id docker kill id and change them to cerebrium ps, cerebrium stop and cerebrium kill. This must be added to cli.

Now that Cerebrium has gone multi-region, we'd like to improve the latency and compliance of our application by running in our region (Mumbai)

We often have to change our scaling configurations based on peak and off peak hours. We've been able to do this manually by calling your REST API. We'd like to be able to scale our apps up and down based on a chron schedule or similar,

I'd like to upload files from their S3 buckets directly to /persistent-storage . Example use case: triggering deployments from a web server, which doesn't have the model files locally. I'd like to avoid having to download data from S3 only to upload to /persistent-storage . Something like cerebrium cp s3://... model/ would be ideal, accepting presigned URLs.

Currently we are able to set an alert that gets sent to our email address when a threshold has been hit. This is limited to once per month. We would like to be able to configure these alerts: Set them as hourly, daily, weekly or monthly thresholds Be able to send these alerts to a communication tool of our choosing (Slack, email, or a webhook) We would also like to the option to terminate all running applications/containers within that space/project when thresholds are hit so that we don't overspend.

This will allow both CPU and GPU applications to start faster

We would like to set up a single billing account that is effective across all of our projects on the platform. Currently, we must set up a new payment method for each project, manage billing access (Our executive committee manage spend) and we receive multiple invoices across all projects.

Allow integrations with Datadog or any external platforms that support OpenTelemetry

I would like to bring my own pre-built Docker images from Dockerhub or AWS ECR (using authentication) and use them on Cerebrium