Security & Compliance dashboard is now in the main UI

The Security & Compliance dashboard has moved out of the legacy dashboard and into the main Aptible UI. It's faster, easier to use, and comes with a refreshed compliance report. Check it out at app.aptible.com/controls.

Note: we're deprecating the legacy Security & Compliance dashboard on Monday, August 31. If you've bookmarked links or built workflows around the legacy version, plan to switch over before then.

Browser-side settings

You can now enable browser-side settings under Settings > Profile > Browser-side settings. When enabled, the UI will try to use previously loaded data for common resources (apps, databases, and more) instead of re-fetching them, so pages load faster on repeat visits.

Persistent Disks for Apps: now available in early access to all organizations

Persistent Disks for Apps, which lets an App Service retain data across deploys, restarts, and container recycles, is now in early access for all organizations. All users can create and attach disks right away, no separate request or setup step required.

Elasticsearch 9.3 and 9.4 are now available

Elasticsearch 9.3 and 9.4 are now available. Descriptions for older image versions that Elastic no longer maintains have been updated to reflect their deprecated status. See docs for more information.

Redis 8.4, 8.6, and 8.8 are now available

Redis 8.4, 8.6, and 8.8 are now available. Descriptions for older image versions that Redis no longer maintains have been updated to reflect their deprecated status. See docs for more information.

New aptible apps:settings command in CLI v0.26.7

The new aptible apps:settings command displays deployment settings for an App, including the configured Docker image and private registry credentials.

Configurable timeouts for the Terraform provider

The Aptible Terraform provider now supports configurable timeouts. If you're running into longer-than-average deployment or provisioning times, you can adjust the timeouts to account for the extra time. See our Terraform Provider docs for more information.

Improvements to runtime health checks

Health checks now run even when a service is scaled to 1 container. Additionally, we've released a bug fix to ensure health checks are properly executed for containers started during a scaling operation with "restart-free scaling" enabled.

Deprecated database versions are blocked from creating public endpoints with unrestricted access

Creating a database endpoint with unrestricted public access is now blocked if the database version is deprecated. This means if your database is deprecated, you will be required to enable IP filtering. See docs for more information.

Invalid custom maintenance page URLs no longer cause deploy failures

Apps and endpoints with an invalid or unreachable custom maintenance page URL will now log a warning and continue the operation rather than fail.

Deprecated environment variables are now disabled

This is a follow-up to the announcement about endpoint and image deployment settings. See the configuration docs for details.

We’re excited to announce that the Aptible LLM Gateway is now available in public beta! The LLM Gateway lets you access LLMs from OpenAI, Anthropic, and Amazon Bedrock through a single, compliant API. It provides HIPAA compliance with BAA coverage, automatic audit logging, and encryption, so your team can use and build AI-powered features without managing compliance infrastructure yourself.

Join the beta today to get $10 of LLM credits to try it out. See docs for more info.

Support for Postgres extension pg_cron

We've added support for pg_cron, a Postgres extension that lets you schedule recurring SQL jobs directly within your database. See docs.

BAAs are now available in the dashboard

A new Agreements page is available in Settings under the Legal and Compliance section. Account Owners can sign new BAAs in-app or send them for signature to a different signer. Once signed, the BAA can be downloaded from the page. Deploy Owners can download a signed BAA but cannot create or sign a new one. A copy of the signed BAA is automatically sent to the signer's email.

Note: Only newly executed BAAs will be shown here. Historical BAAs will not be available. Want to update your BAA on file? Get started here.

Last Deploy timestamp now shows for Apps

The App table and App Details page now display the timestamp of each App's most recent deployment.

Database Backups now show Estimated Monthly Costs

Estimated monthly costs are now shown for individual backups.

Container rightsizing savings now support custo...

The Aptible Home dashboard is now live for all customers. Log in at app.aptible.com and you'll land there automatically.

• Infrastructure overview — counts of your apps, databases, environments, and stacks, plus your estimated monthly cost front and center

• Recently viewed — jump back to the resources you were last working in

• Last deploy — see your most recent deployment, its status, and source/commit info if your app is connected to a repo

• Activity feed — a live snapshot of recent operations across your org, including queued, running, and failed

• Security & compliance — framework status for HIPAA, HITRUST, PCI DSS, plus downloadable compliance badges. New: PCI DSS scoring for all accounts, and PIPEDA for accounts with Canadian resources

• Getting started — a setup checklist for new accounts

We're introducing dedicated Endpoint Settings and Image Deployment Settings: a first-class way to configure per-endpoint behavior and image-based deployments separately from your app's environment variables.

What's changing

Until now, two categories of configuration were managed through special app environment variables:

• Endpoint behavior — variables like FORCE_SSL, IDLE_TIMEOUT, SSL_PROTOCOLS_OVERRIDE, and STRICT_HEALTH_CHECKS controlled how each endpoint handled traffic, but because they lived in the app environment, every endpoint shared the same values with no way to configure them independently.

• Image deployment — variables like APTIBLE_DOCKER_IMAGE, APTIBLE_PRIVATE_REGISTRY_USERNAME, and APTIBLE_PRIVATE_REGISTRY_PASSWORD specified which image to deploy and how to pull it, but mixing these into the app environment meant they were visible as runtime env vars inside your containers, and in Terraform, made certain types of changes harder than they should have been.

With this release, both are now managed through dedicated settings — endpoints get per-endpoint configuration, and image deployment details live in app-level settings, separate from the container environment.

What's new

• UI: Endpoint settings are now editable directly on each endpoint's configuration page. Image deployment settings are managed on the app's deployment configuration page.

• CLI: Update to aptible-cli v0.26.6 for aptible endpoints:https:modify --force-ssl ... and aptible deploy --docker-image ... style commands now write to settings rather than env.

  • Terraform: Update to aptible/aptible v0.10.0 — the aptible_endpoint and aptible_app resources now accept these as parameters. Consult the Aptible Terraform provider documentation for examples.

Why this matters

Beyond cleaner separation of concerns, this unlocks something that wasn’t possible before: each endpoint can now have independent settings.

• Enforce SSL on one endpoint while leaving another flexible.

• Set different idle timeouts per endpoint.

  ...

Token generation & SIEM setup

Setting up a SIEM integration for Activity is now simpler. Any user can now generate a long-lived Activity Logs token directly from Settings → Tokens, without a special role. The token grants read-only access to the activity logs that the user can already see, along with the organizational metadata needed to retrieve them.

For organization-wide coverage, create a dedicated service user and add them to the Activity Log Viewer role - a built-in role purpose-built for SIEM use cases. This built-in role provides read-only access to all activity across your organization and is purpose-built for use cases like SIEM integrations.

Tokens can be valid for up to a year. If one expires, your integration will resume from its last saved position as soon as you rotate in a fresh token to ensure no activity gaps.

Deleted resource visibility

Operations logs for deleted resources are now surfaced on the Activity page, with a 90-day lookback window. Deleted databases also have a new dedicated Backups tab where you can restore or purge backups directly.

Dashboard home improvements

New Container Efficiency widget for at-a-glance resource utilization:

The Activity Feed table has been updated to match the full Activity page.

Improved container profile selection

When selecting a container profile (M, C, or R) in the UI, generation (legacy or non-legacy) is no longer available as a selection. Instead, Aptible will always attempt to choose the latest supported generation with available capacity. If you specify a generation via the CLI (as an argument to --container-profile), the generation will be ignored. For example, m5 will be interpreted simply as m.

DEPRECATION NOTICE: Starting with v0.9.23, the Aptible Terraform provider will no longer accept container profiles with generation numbers (e.g. m4, m5, r5, c5, etc.) as arguments to container_profile for aptible_app and aptible_database resources. If you upgrade your provider you will be forced to select

The AI Gateway now gives you full visibility into your LLM requests — both in the Aptible UI for day-to-day troubleshooting and via log drain integrations for long-term compliance and observability.

View request and response logs in the UI

You can now view the full contents of your LLM requests and responses directly in the Aptible UI. From the key details page, click into any request to see the complete request and response payloads. Use this to verify your gateway configuration, refine prompts, and troubleshoot issues without leaving the product.

Stream logs to Langfuse

You can now configure a Langfuse log drain from the Aptible UI to send your full LLM request and response logs to Langfuse for prompt management, observability, and analysis. LLM trace drains are configured at the environment level in the Integrations tab.

A note about Anthropic models

We now support accessing Anthropic models through Bedrock, e.g. bedrock/anthropic.claude-sonnet-4-6 instead of anthropic/claude-sonnet-4-6. In the near future, we plan to fully transition to only supporting Anthropic models through bedrock/anthropic — please update your existing Anthropic usage accordingly.

In our effort to keep making it easier to maintain a rigorous disaster recovery posture on Aptible, we've added Point-in-time Recovery (PITR) capabilities for Aptible Managed PostgreSQL databases, at no additional charge.

PITR is enabled by default for all PostgreSQL databases (with a few exceptions noted in our docs, like EOL versions or databases with backups disabled). Some databases must be restarted in order to (automatically) enable PITR; for other databases, PITR is already enabled. To check whether PITR is enabled for any of your PostgreSQL databases, refer to the Backups column on the Databases list view, or the Point-in-Time Recovery attribute on any database's detail page.

To restore any PITR-enabled database to a specific point in time in a new database, visit the Recovery tab on that database's detail page, and provide: a name for the new database, and the timestamp to which you'd like to restore. Currently, we limit PITR restores to timestamps in the last 24 hours. If your use case requires restoring to a point in time older than 24 hours, please let us know in Slack or via a support ticket.

If you have any questions about how PITR works or how to use it, check out our docs on PITR!

Activity: more visibility, better filtering

• Activity now includes operations for deleted resources, with full drill-down into historical events

• Added read-only activity tracking (e.g., sensitive access events), available via the Show Read-Only filter

• Activity events can now be streamed to your SIEM or logging provider for centralized monitoring, alerting, and compliance workflows

• Improved table experience, including the ability to customize visible columns

• Updated operation naming in UI for clarity. For example:

  • membership.create → Role Add User

  • membership.destroy → Role Remove User

  • permission.create → Role Add Permission

  • permission.destroy → Role Remove Permission

• Activity can now be filtered by text-based search

• Automated activities now clearly identified as automated

View Activity here

Container Efficiency (formerly scaling recommendations)

• Scaling recommendations are now presented as Container Efficiency

  • “Scale Down” → Over-provisioned

  • “Scale Up” → Under-provisioned

• Added a tooltip to view usage stats and rationale

View Container Efficiency for App Services here ...

The AI Gateway now offers more granular spend data and key request history to help you understand and optimize your LLM usage.

Spend data by key

In the keys list and the key details page, you can see the spend during the current usage period for each key. Use this to understand which keys are most active, and which use cases might benefit from cost optimization.

Request history and spend data by request

In the key details page, you can see all the requests made by the key in the last 7 days, including token usage and cost information.

Coming soon: view the contents of your LLM request and response logs to help with prompt refinement and troubleshooting.

Aptible AI Gateway (beta) now includes model access policies and cost visibility. 

Access Policies

Use model access policies to ensure that your applications and developers are using the right model for the job. Model access policies are set at the environment level and apply to all keys within that environment. 

Cost Visibility

View LLM usage at the environment and global level to understand your spend and remaining budget for the month. Coming soon: view costs at the key and request level to understand and optimize more granular usage.

Aptible AI Gateway is currently in beta. Contact Aptible Support to join.

Based on feedback, we've made major improvements to our Activity page (video demo):

• Comprehensive data - All platform actions are captured, now including auth events (successful/failed logins, role changes, and more) and deleted resources

• Unlimited lookback - Going forward, the Activity page supports unlimited lookback, compared to the previous 7-day limit

• Improved search/speed - Multi-select filters (by user, time range, activity type, or environment) and 5x faster responses on average

  
  

Try it out here: https://app.aptible.com/activity

Read the docs here for more information on activity.

We’re continuing to build on this, with CSV export, full-text search, API docs, and SIEM integrations coming soon. We’d love your feedback! Share thoughts in the thread here or upvote/submit ideas on our public roadmap.

We are happy to announce that Elasticsearch versions 8.17 through 9.2 are now available on Aptible. These versions introduce a significant number of enhancements and features to ElasticSearch, including improvements to performance, vector search, and semantic modeling. Since this is a significant upgrade from our previously offered version of Elasticsearch 7.10, we recommend that users review the Elasticsearch release notes closely for compatibility.

Additionally, due to the lack of open-source versions between Elasticsearch 7.10 and 8.17, we will not be able to offer any in-place database upgrades at this time. We advise customers to provision new databases or use ElasticSearch’s snapshot and restore API (such as the S3 repository plugin) to transfer indices to a newer version.

Other releases

• Improvements to the new UI Home page - currently in Open BETA

  • Recently Viewed widget: New widget on the Home dashboard to see recently viewed resources.

  • Last Deploy widget: New widget on the Home dashboard to see your last deploy app, the status of the deploy, and commit data.

• VPC Peering requests (creations and deletions) can now be requested in the UI by account owners

This feature is part of our Managed AI initiative, designed to make it easier to deploy, run, and scale AI applications with Aptible. Need something else for your AI apps? Let us know.

We've launched a beta of our new LLM gateway product, which gives you an easy way to use LLMs with built-in compliance features. You can generate LLM keys through the Aptible UI, and your usage will be HIPAA-compliant through BAA coverage for models, automatic audit logging, data encryption, and no PHI retention for model training.

If you're interested in joining the beta, contact Aptible Support

PostgreSQL 18

We are happy to announce that PostgreSQL 18 is now available on Aptible. PostgreSQL 18 introduces several new features and enhancements, such as a new asynchronous I/O system for certain operations like vacuum, and improved locking performance for queries that access multiple relations. Additionally, there’s a significant number of smaller improvements associated with this release, so we recommend reading through the official release notes for PostgreSQL 18. Please reach out to Aptible Support if you have any questions.

New Open BETAS

• Point-in-time Recovery for PostgreSQL: Point-in-time recovery (PITR) for PostgreSQL is now available in public BETA! Check out the docs here and contact Aptible Support if you're interested in enabling.

• Home page in Aptible Dashboard: We've launched a new home page for the Aptible dashboard in BETA. We plan to continue iterating and making changes here over the next few weeks so we can showcase the most relevant information to you. Want access or have feedback? Contact Aptible Support!

Other releases:

• New cross-region copy region for ap-southeast-2: Database backups taken within the ap-southeast-2 region will now be copied to ap-southeast-4, going forward, when the environment's cross-region copy setting is enabled. This update allows for continuous compliance with Australian data requirements.

• Improved Scaling Recommendations data: We've updated our in-app scaling recommendations to include more data, allowing you to better understand the recommendations being made.

• Fix - Failing/incomplete loading for in-app metrics: We released a fix for an issue that occasionally caused failure or incomplete loading of in-app metrics for services with many containers.

InfluxDB 1.11 and 1.12

We are happy to announce that InfluxDB 1.11 and 1.12 are now available on Aptible. As the first public releases of InfluxDB v1 since 2021, these versions include multiple enhancements and bug fixes, which can be reviewed in InfluxData’s changelog.

These database versions are available now and can be provisioned through the UI and CLI. If you’re looking to upgrade an existing instance of InfluxDB v1, please reach out to Aptible Support.

RabbitMQ 4.1 and 4.2

We are happy to announce that RabbitMQ 4.1 and 4.2 are now available on Aptible. These feature releases include performance improvements as well as some minor enhancements. You can read more about each version in the release notes:

• RabbitMQ 4.1 Release Notes

• RabbitMQ 4.2 Release Notes

These database versions are available now and can be provisioned through the UI and CLI. If you’re interested in upgrading an existing RabbitMQ database to one of these versions, please reach out to Aptible Support.

Other releases

• MySQL Updates:

  • New Minor Version Available: MySQL 8.0.44 and 8.4.7 are now available

  • MySQL replicas are now read-only by default

  • Restoring a backup of a MySQL replica will disable replication by default to give users more control over the recovery process.

• Invoices: Invoices are now available in our main UI. Previously, they were only accessible through our legacy dashboard.

  • Tip: You can now give access to users other than Account Owners with the new Billing Only Role.

• New Search Tags: You can now filter resources using new search tags:

We are happy to announce that Redis 7.2, 8.0, and 8.2 are now available on Aptible. Each version introduces performance optimizations and new capabilities to improve the efficiency, usability, and security of Redis databases. You can learn more about each version in Redis’ official documentation, which we’ve linked below for convenience.

• What’s New in Redis 7.2

• What’s New in Redis 8.0

• What’s New in Redis 8.2

A new Billing-Only Role is now available in all accounts. This role lets you grant team members access to billing-related tasks—such as viewing and managing invoices and payment methods—without adding or modifying access to any Aptible resources.This makes it easy to:

• Provide your Finance team with billing access without granting access to any resources: apps, databases, or environments

• Give a developer visibility into invoices without changing their resource access

Only Account Owners can add or remove users from the Billing-Only Role. Users in this role cannot invite others or modify role assignment. Visit the Roles page to get started.

Other releases:

• Shared Endpoints improvements:

  • Migrating to, or modifying certain attributes of, a shared endpoint now waits longer for existing connections to close naturally

  • Endpoints now display whether Shared Endpoints can be enabled. For example, non-ALB endpoints show “Shared Endpoints = N/A” so it’s clear the option doesn’t apply.

  • You can now also use the shared:no search tag within the endpoints page to see a list of potential shared endpoints. Quick link here

• IDLE_TIMEOUT value also now sets the HTTP client keep-alive setting for HTTPS Endpoints. Related docs.

• Autoscaling operations are no longer enqueued while configure operations are running.

• The Database overview table and individual Database details now display whether backups are enabled or disabled.

• You can now request a Dedicated Stack to be deprovisioned directly in the Aptible Dashboard. Navigate to the Dedicated Stack’s Settings tab to use this.

  
  

Aptible will be deprecating Companion Git Repositories starting today, September 15th. Customers will have until November 3rd, 2025 to migrate.

What is a Companion Git Repository, and why is it being removed?

Initially, Aptible supported deploying applications only via Git: customers provided a Dockerfile, and the platform built the app image. In June 2017, we added support for deploying pre-built Docker images. At that time, if you needed to define processes or migrations using a Procfile or .aptible.yml, those files still had to be provided via Git in addition to your image. This pattern of providing configuration files via Git is known as a Companion Git Repository. In January 2018, we added support to provide Procfiles and .aptible.yml directly within Docker Images. At that time we indicated that the Companion Git Repository was deprecated, but gave an indefinite timeline for customers to migrate. In order to continue to modernize and simplify our platform, we’re finally taking action to require customers to stop using this deprecated feature.

What impact will this have on me?

Hopefully, none! Fewer than 2% of apps hosted on Aptible use a Companion Git Repository, and even fewer include a Procfile or .aptible.yml. Since there is no functional difference in how these files are provided, migrating off the deprecated method will not affect app behavior. If you’re one of the impacted customers, we’ve already contacted your Ops Alert contact directly and provided them with a list of affected apps.

Starting today, impacted apps will fail to deploy. You can either:

• Migrate your app immediately, using the "How do I migrate?" section of our documentation

• Temporarily opt-in to continue using the feature by acknowledging the deprecation for each impacted App. See “Using Companion Git Repositories during deprecation” in the documentation here.

On November 3rd, 2025, the opt-in behavior will be removed, and you will be required to migrate any remaining Apps before deploying them again.