Hosted Applications

Scaling settings define how hosted deployments associated with an application add or remove replicas to handle load. You set a minimum and maximum number of replicas and select an autoscaling metric, such as concurrent requests, requests per second (RPS), CPU utilization, or memory utilization.

For applications with persistent file storage, set the minimum and maximum replica counts to 1. Persistent file storage supports one replica in this release.

Managed storage provides stateful storage for hosted deployments associated with an application. File Storage is mounted at a container path that you specify. Database and cache connection details are provided through environment variables.

You can also define other runtime variables that are injected into the container at runtime.

Authentication settings control how requests are authenticated before they're routed to the hosted deployment. Hosted applications support identity domain bearer token, identity domain browser session, and OCI IAM request-signature authentication. You can also select No authentication for public content or when your application manages authentication. Associated hosted deployments inherit the application's settings.

Identity domain browser session authentication uses the OAuth 2.1 Authorization Code flow with PKCE. The service obtains access tokens on behalf of browser users and establishes sessions that use cookies. With No authentication, the platform doesn't authenticate incoming requests. If access needs restriction, your application must enforce the required authentication and authorization controls. See Authentication.

To view the selected setting after creation, open the application's Configuration tab and check Authentication type under Authentication.

Networking settings control how hosted deployments associated with an application route outbound traffic (egress) and how the active deployment is accessed through a public or private endpoint.

By default, each deployed application is configured with outbound access to the public internet. This allows agent workloads to reach external resources such as public MCP servers, third-party APIs, foundation model endpoints, and other internet-hosted tools required for typical AI workflows.

An application can also operate in Customer Networking Mode. For this option, you specify a target subnet within a VCN in the tenancy. The platform then establishes a secure private network connection between the agent workload and the selected subnet using a Private Endpoint / Reverse Connection Endpoint (PE/RCE) mechanism.

After enabled, all outbound (egress) traffic from the agent is routed through the customer-specified subnet. As a result:

• The agent can securely access private resources within your network (for example, databases, Compute instances, internal services).
• Traffic remains within private network boundaries.
• Network security controls such as network security groups, (NSG)s, route tables, and firewalls in your VCN govern outbound connectivity.
• Public internet egress can be restricted or disabled according to enterprise security requirements.

This model provides flexibility to support both internet-facing AI workloads and fully private, enterprise-integrated deployments, while maintaining clear network isolation boundaries between the platform and customer environments.

By default, each deployed application is provisioned with a public endpoint that allows your clients to invoke the agent over the internet, subject to configured authentication and authorization controls.

For use cases requiring private network access, you can create a Private Endpoint (PE) within the GenAI platform. The Private Endpoint enables invocation through a private IP address and internal DNS resolution. Clients within the connected private network (for example, VCN, on-premises through FastConnect/VPN, or peered networks) can then invoke the agent using the Private Endpoint’s fully qualified domain name (FQDN).

This setup enables:

• Elimination of public internet exposure
• Traffic confinement within private network boundaries
• Alignment with enterprise network security and compliance requirements

After an agent is deployed, clients invoke it through the provisioned endpoint. The transport protocol depends on the agent server implementation and the interaction model required (request/response, streaming, or bidirectional sessions).

The supported protocols include:

AI agents require stateful services to support short-term memory, checkpoints, caching, and context storage. To simplify operations and reduce management overhead, the platform provides fully managed storage for hosted applications.

When deploying an agent, you can select one or more of the following managed storage options:

• File Storage
• PostgreSQL
• OCI Cache
• Oracle Autonomous Database

You can attach one resource of each storage type. The service provisions or attaches the selected storage and configures the application's access.

File Storage retains files at a designated mount path across container restarts and redeployments. Each application-specific attachment has a fixed 50 GB quota. Applications using the same storage resource receive separate file systems and don't share files. See Persistent File Storage for Hosted Applications.

For limits such as the number of allowed applications or artifacts per tenancy, see Application Limits

You can perform the following tasks to create and list applications:

• Creating an application
• Listing applications