# heroku Published articles for heroku. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Six Heroku CLI Commands for Improving Terminal Workflows DevFeed: [Six Heroku CLI Commands for Improving Terminal Workflows]() Original publisher: [Read original article]() Author: Andy Smith Published: 2026-08-25T16:28:53Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Command-line interface](), [Heroku](), [Developer experience](), [code productivity]() Tags: [cli](), [command-line](), [commands](), [config](), [developer-experience](), [developer-tools](), [ecosystem](), [heroku](), [heroku-postgres](), [productivity](), [terminal](), [tools](), [variables]() ### AI overview This tutorial presents six Heroku CLI commands intended to reduce context switching and improve terminal-based workflows. The supplied content discusses exporting app configuration for local environments and checking active Heroku Postgres database queries, while warning about production configuration handling and credential leaks. ### Source excerpt Improving developer experience in the command line relies on minimizing context switches. While most engineers use the Heroku CLI strictly for basic tasks like pushing code, it contains a powerful suite of command line tools built to optimize your workflow. If you want to keep your focus locked on writing code, these six Heroku CLI commands will instantly upgrade your daily productivity. The post 6 Lesser-Known Heroku CLI Commands You Probably Aren't Using appeared first on Heroku. ## Fine-Grained Access Control Now Available for All Heroku Customers DevFeed: [Fine-Grained Access Control Now Available for All Heroku Customers]() Original publisher: [Read original article]() Author: Alberto Sigismondi Published: 2026-08-21T17:07:29Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Access Control](), [Security](), [IAM](), [Zero Trust](), [legacy]() Tags: [access-control](), [deploy](), [heroku](), [iam](), [identity-and-access-management](), [least-privilege](), [legacy](), [news](), [permissions](), [pipelines](), [security](), [security-compliance](), [zero-trust]() ### AI overview Heroku announces that Fine-Grained Access Control is available to all customers. The feature replaces fixed legacy roles with capability-based roles and app-specific permissions for roles such as view, deploy, operate, and manage. ### Source excerpt Fine-Grained Access Controls is now available to all Heroku customers. Heroku's legacy system gave you predefined roles like admin, member, or collaborator, each with a fixed bundle of permissions. It replaces that system with fine-grained roles like view, deploy, operate, and manage, with specific capability sets. Access control is managed at an app-specific layer, giving [...] The post Fine-Grained Access Control Now Available for All Heroku Customers appeared first on Heroku. ## How To Set Up a Staging Environment on Heroku in 3 Easy Steps DevFeed: [How To Set Up a Staging Environment on Heroku in 3 Easy Steps]() Original publisher: [Read original article]() Author: Andy Smith Published: 2026-07-16T18:23:58Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Deployment](), [Continuous Delivery (CD)](), [Testing](), [pull-requests](), [Git](), [GitHub]() Tags: [continuous-delivery](), [continuous-deployment](), [deployment](), [engineering](), [github](), [heroku](), [heroku-pipelines](), [how-to](), [pull-requests](), [testing]() ### AI overview A tutorial explains how to create a staging environment on Heroku by separating configuration and databases, grouping applications in Heroku Pipelines, and promoting tested compiled slugs to production. It also covers continuous delivery, disabling automatic deployment during setup, and optional Review Apps for pull requests. ### Source excerpt Moving fast should not mean breaking things for your users. While testing on localhost is a good start, you need a near identical replica of production to catch any bugs before your code goes live. That is where a staging environment comes in. Heroku pipelines handle the infrastructure layout for you, keeping your deployment workflow clean and automated. The post How To Set Up a Staging Environment on Heroku in 3 Easy Steps appeared first on Heroku. ## Securing Heroku CLI Credentials with System Keychain Storage DevFeed: [Securing Heroku CLI Credentials with System Keychain Storage]() Original publisher: [Read original article]() Author: Katy Bowman Published: 2026-07-01T21:11:54Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Authentication](), [Command-line interface](), [Security](), [sensitive data]() Tags: [authentication](), [cli](), [compatibility](), [credentials](), [engineering](), [heroku](), [linux](), [macos](), [security](), [sensitive-data](), [storage](), [windows]() ### AI overview Heroku CLI version 11.8.0 makes system keychain storage the default for authentication credentials. The credential manager uses native secure storage on macOS, Linux, and Windows while preserving netrc compatibility and file-based fallback options. ### Source excerpt Beginning in version 11.8.0, we will be improving the security of the Heroku CLI by storing authentication credentials in your system keychain by default. The Heroku credential manager makes use of OS-native secure storage tools with interfaces designed for sensitive data while maintaining compatibility with existing developer workflows. We began the transition to our new [...] The post Securing Heroku CLI Credentials with System Keychain Storage appeared first on Heroku. ## A 15-Second Health Check for Your Heroku Connect Data Pipeline DevFeed: [A 15-Second Health Check for Your Heroku Connect Data Pipeline]() Original publisher: [Read original article]() Author: Nick Prey Published: 2026-06-24T15:35:14Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [Data Management](), [SQL](), [Databases]() Tags: [cli](), [data-pipeline](), [engineering](), [heroku](), [heroku-connect](), [migrations](), [salesforce](), [schema](), [synchronization](), [troubleshooting]() ### AI overview This tutorial explains how the Heroku Connect CLI plugin's diagnostic command checks connection health, schema alignment, and field configurations in a Salesforce-to-Heroku Postgres data pipeline. It highlights how the command can expose configuration mismatches and provide actionable warnings before schema updates or migrations. ### Source excerpt Heroku Connect is a fully managed, bidirectional data sync service between Salesforce and Heroku Postgres that lets developers read and write Salesforce data using standard SQL. The sync is straightforward to set up and operates smoothly in the background, but when a field does not update as expected or data seems to lag, you do not need to guess what went wrong. The post A 15-Second Health Check for Your Heroku Connect Data Pipeline appeared first on Heroku. ## Modernizing the Command Line: Heroku CLI v11 DevFeed: [Modernizing the Command Line: Heroku CLI v11]() Original publisher: [Read original article]() Author: Eric Black Published: 2026-03-19T22:29:49Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [ECMAScript](), [modules](), [migration](), [maintenance](), [Usability]() Tags: [cli](), [command-line](), [heroku](), [javascript](), [legacy](), [maintainability](), [migration](), [modules](), [monorepo](), [news](), [node-js](), [npm](), [performance](), [release](), [upgrade](), [usability]() ### AI overview Heroku CLI v11 is available with a migration to ECMAScript Modules and oclif v4. The release also changes the build system from Yarn to npm, removes the monorepo structure, improves command execution and manifest caching, and adds semantic colors and theme support. ### Source excerpt Heroku CLI v11 is now available. This release represents the most significant architectural overhaul in years, completing our migration to ECMAScript Modules (ESM) and oclif v4. This modernization brings faster performance, a new semantic color system, and aligns the CLI with modern JavaScript standards. While v11 introduces breaking changes to legacy namespaces, the benefits are [...] The post Modernizing the Command Line: Heroku CLI v11 appeared first on Heroku. ## Bigger Slugs and Greater Build Timeout Flexibility DevFeed: [Bigger Slugs and Greater Build Timeout Flexibility]() Original publisher: [Read original article]() Author: Jesse Brown Published: 2026-03-19T22:28:36Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Deployment](), [container]() Tags: [buildpacks](), [deployment](), [developer](), [dynos](), [heroku](), [news](), [platform-updates](), [timeout]() ### AI overview Heroku increased the default maximum compressed app slug size from 500MB to 1GB and raised build compile timeouts. The update supports applications with large dependencies, while larger slugs may increase dyno boot times. ### Source excerpt Modern applications, especially those leveraging AI and data-heavy libraries, need more room to breathe. To support these evolving stacks and reduce developer friction, we've increased the default maximum compressed slug size from 500MB to 1GB. Understanding app slugs and deployment App slugs are the container build artifacts produced by Heroku Buildpacks and run in dynos. [...] The post Bigger Slugs and Greater Build Timeout Flexibility appeared first on Heroku. ## Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku DevFeed: [Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku]() Original publisher: [Read original article]() Author: Juan Bustamante Published: 2026-03-17T15:00:03Z Content type: opinion Language: en Sources: [Heroku]() Topics: [Heroku](), [Maintainers](), [Cloud Native Ecosystem](), [Command-line interface](), [releases](), [Security](), [vulnerability](), [GitHub Actions](), [GitHub](), [GitHub Issues](), [Google Cloud Platform (GCP)](), [Docker]() Tags: [buildpacks](), [cli](), [cloud](), [cloud-infrastructure](), [cloud-native](), [cloud-native-ecosystem](), [docker](), [ecosystem](), [engineering](), [github](), [github-actions](), [github-issues](), [google-cloud](), [google-cloud-run](), [heroku](), [maintainers](), [maintenance](), [open-source](), [patches](), [platform](), [releases](), [security](), [vulnerability]() ### AI overview This article describes how pack CLI maintainers support Cloud Native Buildpacks through releases, security patches, issue triage, pull request reviews, CI changes, and feature development. It explains how Heroku-funded maintenance benefits Heroku, Google Cloud Run, and internal platform teams. ### Source excerpt Most developers never see the 11 pack releases we shipped in the last 14 months as pack CLI maintainers. That's actually a good sign--it means the infrastructure just works. When a critical vulnerability emerges requiring an immediate upgrade, the fix is shipped within days. Here's what most developers don't see: that same security patch now [...] The post Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku appeared first on Heroku. ## Deploy Smarter with AI: Introducing App Platform Skills on DigitalOcean DevFeed: [Deploy Smarter with AI: Introducing App Platform Skills on DigitalOcean]() Original publisher: [Read original article]() Author: Ritesh Mahato Published: 2026-03-16T14:00:00Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Deployment](), [Artificial Intelligence](), [Open Source](), [GitHub Actions](), [migration](), [PostgreSQL](), [VPC](), [SSL](), [Heroku]() Tags: [ai](), [deployment](), [digitalocean](), [github-actions](), [heroku](), [migration](), [open-source](), [platform](), [postgresql](), [product-updates](), [skills](), [ssl](), [vpc]() ### AI overview DigitalOcean introduces App Platform Skills, a collection of open-source playbooks that provide AI assistants with current, opinionated knowledge for designing, deploying, and troubleshooting applications on DigitalOcean App Platform. ### Source excerpt AI coding assistants have fundamentally changed how developers write software. Tools like Claude Code, Codex, GitHub Copilot, Gemini, and Cursor can scaffold an entire application in minutes. But ask any of them to deploy that application to a production cloud environment, and the experience breaks down -- not because models lack intelligence, but because they lack current, opinionated infrastructure knowledge. Cloud platforms evolve faster than training data refreshes: instance sizes change, new features ship, and battle-tested best practices emerge from customer feedback that never makes it into public documentation. Today, we're announcing App Platform Skills, a collection of open-source, AI-native playbooks that bridge this gap. Skills inject up-to-date, opinionated DigitalOcean App Platform knowledge directly into your AI assistant's context -- turning it from a generic code generator into an infrastructure-aware co-pilot that understands deployment models, networking primitives, database bindings, and operational patterns. Shell npx skills add digitalocean-labs/do-app-platform-skills That single command gives your AI assistant access to 12 specialized skills covering everything from greenfield app design to Heroku migration to production troubleshooting. Benefits -Production-Ready from the Start: Skills encode patterns from thousands of real deployments -- VPC networking by default, PostgreSQL v16 with SSL required, credentials in GitHub Secrets -- so AI-generated configuration aligns with how experienced platform engineers actually build. -Composable Skill Chaining: Skills work together. Describe a new app to the designer skill, and the planner skill decomposes deployment into staged phases while the deployment skill generates a GitHub Actions workflow to execute the rollout. -Zero Credential Exposure: The AI agent never handles sensitive credentials directly. Workflows reference GitHub Secrets by name, managed services use bindable variables like ${db.DATABASE_U ## From Fragmented Logs to Full-Stack Visibility with SolarWinds Papertrail DevFeed: [From Fragmented Logs to Full-Stack Visibility with SolarWinds Papertrail]() Original publisher: [Read original article]() Author: Rachel Revoy Published: 2026-03-12T15:00:36Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [observability](), [Logging](), [Monitoring](), [solarwinds]() Tags: [add-ons](), [apis](), [databases](), [developer-tools](), [dynos](), [ecosystem](), [engineering](), [heroku](), [logs](), [metrics](), [monitoring](), [observability](), [solarwinds]() ### AI overview The article describes how fragmented logs, metrics, deployment activity, and monitoring dashboards complicate troubleshooting for applications running on Heroku. It presents the expanded SolarWinds Papertrail add-on as a unified solution for delivering logs and metrics together. ### Source excerpt Modern applications on Heroku don't just consist of code. They are living ecosystems comprised of dynos, databases, third-party APIs, and complex user interactions. As these systems scale, so do the logs and metrics. To efficiently extract the signals from the noise you need to understand system health in the context of external factors, like resource [...] The post From Fragmented Logs to Full-Stack Visibility with SolarWinds Papertrail appeared first on Heroku. ## How continuous deployment and coding agents are changing software development DevFeed: [How continuous deployment and coding agents are changing software development]() Original publisher: [Read original article]() Published: 2026-03-11T14:30:00Z Content type: opinion Language: en Sources: [Will Larson - Irrational Exuberance]() Topics: [CI/CD](), [Deployment](), [migration](), [AI-assisted coding](), [Heroku]() Tags: [coding-agents](), [continuous-deployment](), [deployment](), [heroku](), [migration]() ### AI overview The author contrasts manual deployment and database migration practices at Imprint with a later workflow in which most changes continuously deploy to production after pull-request review and merge. The article connects this migration to broader reflections on how coding agents may affect software development. ### Source excerpt When I joined Imprint a little less than a year ago, our deploys were manual, requiring close human attention to complete. Our database migrations were run manually, too. Developing good software is very possible in those circumstances, but it takes a remarkable attention to detail to do it. It was also possible to develop good software using Subversion and developing by ssh'ing into a remote server to edit PHP files, but the goal is making things easy rather than possible. Ten months later, the vast majority of our changes, including database migrations, continuously deploy to production without human involvement after the initial pull request is reviewed and merged. Reading aloud the relevant pages from the mandated gospel of continuous deployment, deploying changes this way doesn't make them less reliable, but more so. Each step of validation a human might do, is now consistently done on every deploy, including many steps that are just onerous enough to drop off the standard operating steps like meticulously checking the post-launch health on a production canary every minute for half an hour after each deploy. This migration has reminded me a lot of the Uber service migration, which prompted me to write Migrations: the only scalable solution for technical debt back in 2018, and in particular how different this sort of migration feels in the age of coding agents. The more I've thought about how these two migrations compared, the more it's solidified my thinking a bit about how this technology is going to impact software development over the next few years. Migrations as metaphor Although I really want to talk about how coding agents are changing software development, I want to start by expanding a bit on this recent migration at Imprint and how it compared with the migration at Uber. The Uber migration was: Spinning up a new self-service service provisioning platform, along the lines of a very minimal Heroku, including the actual scheduling algorithm across cluste ## Preparing for Shorter SSL/TLS Certificate Lifetimes DevFeed: [Preparing for Shorter SSL/TLS Certificate Lifetimes]() Original publisher: [Read original article]() Author: Emily Huang Published: 2026-03-06T16:50:10Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [TLS (Transport Layer Security)](), [certificates](), [AWS Certificate Manager](), [maintenance](), [Security]() Tags: [automation](), [certificates](), [heroku](), [maintenance](), [news](), [security](), [ssl](), [tls]() ### AI overview Heroku explains that publicly trusted SSL/TLS certificates will have shorter maximum lifetimes, with a 200-day maximum beginning March 15, 2026. Users who manually manage certificates for Heroku applications will need more frequent renewals, while Heroku Automated Certificate Management handles certificate renewal automatically. ### Source excerpt The web browser and certificate authority industry is shortening the maximum allowed lifetime of TLS certificates. These changes will improve security on the Web, but you may have to change certificate maintenance practices for apps you run on Heroku. The good news is that if you're using Heroku Automated Certificate Management, no changes are required: [...] The post Preparing for Shorter SSL/TLS Certificate Lifetimes appeared first on Heroku. ## Heroku AI adds a flexible standard plan and expands its managed model catalog DevFeed: [Heroku AI adds a flexible standard plan and expands its managed model catalog]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2026-02-19T17:08:20Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku AI](), [Heroku](), [model-deployment](), [Claude](), [deepseek](), [cohere]() Tags: [claude](), [cohere](), [deepseek](), [deployment](), [heroku](), [heroku-ai](), [inference](), [managed-inference-and-agents](), [models](), [news](), [updates]() ### AI overview Heroku introduces a standard plan for Managed Inference and Agents that lets developers access supported models through one add-on and API key, while adding Claude 4.6, new open-weight models, and Cohere Embed V4. ### Source excerpt Heroku is introducing significant updates to Managed Inference and Agents. These changes focus on reducing developer friction, expanding model catalogue, and streamlining deployment workflows. More flexibility with the new standard plan Until now, Heroku's model-based plans required developers to provision a specific add-on for a specific model. This created significant operational overhead. If you wanted [...] The post Whats New in Heroku AI: New Models and a Flexible Standard Plan appeared first on Heroku. ## Code Execution Sandbox for Agents on Heroku DevFeed: [Code Execution Sandbox for Agents on Heroku]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2026-02-17T20:34:33Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Code](), [container](), [Model Context Protocol (MCP)](), [Claude]() Tags: [agents](), [claude](), [code](), [container](), [execution](), [heroku](), [heroku-ai](), [managed-inference-and-agents](), [mcp](), [mcp-on-heroku](), [news](), [sandbox]() ### AI overview Heroku describes code execution sandboxes for AI agents, using ephemeral one-off dynos to isolate untrusted code. The article explains built-in and MCP-based integrations and how programmatic tool calling can reduce context usage. ### Source excerpt Large language models are good at writing code. Data from Anthropic shows that allowing Claude to execute scripts, rather than relying on sequential tool calls, reduces token consumption by an average of 37%, with some use cases seeing reductions as high as 98%. Untrusted code needs a secure and isolated place to execute. We solved [...] The post Code Execution Sandbox for Agents on Heroku appeared first on Heroku. ## Building AI-Powered Observability with Heroku Managed Inference and Agents DevFeed: [Building AI-Powered Observability with Heroku Managed Inference and Agents]() Original publisher: [Read original article]() Author: Karunasri (Karuna) Garigipati Published: 2026-02-13T19:36:30Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Model Context Protocol](), [observability](), [telemetry](), [Artificial Intelligence](), [ide]() Tags: [ai](), [developer-tools](), [engineering](), [heroku](), [ide](), [incident](), [managed-inference-and-agents](), [mcp-on-heroku](), [model-context-protocol](), [observability]() ### AI overview This tutorial explains how to connect AI coding assistants in an IDE to observability platforms such as Splunk, Honeycomb, and Sentry through the Model Context Protocol and Heroku Managed Inference and Agents. It describes exposing platform APIs as MCP tools so engineers can query production telemetry in plain English and correlate issues across platforms. ### Source excerpt If you've ever debugged a production incident, you know the drill: IDE on one screen, Splunk on another, Sentry open in a third tab, frantically copying error messages between windows while your PagerDuty keeps buzzing. You ask "What errors spiked in the last hour?" but instead of an answer, you have to context-switch, recall complex [...] The post Building AI-Powered Observability with Heroku Managed Inference and Agents appeared first on Heroku. ## Heroku and GitHub Enterprise Server: Stronger Security, Seamless Delivery DevFeed: [Heroku and GitHub Enterprise Server: Stronger Security, Seamless Delivery]() Original publisher: [Read original article]() Author: Alberto Sigismondi Published: 2026-02-11T22:08:19Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [GitHub](), [Security](), [CI/CD](), [GitHub Actions](), [OAuth](), [Terraform]() Tags: [ci-cd](), [deployment](), [devops](), [ecosystem](), [github](), [github-actions](), [heroku](), [heroku-enterprise](), [heroku-flow](), [integrations](), [news](), [oauth](), [security](), [terraform]() ### AI overview Heroku announces the general availability of its GitHub Enterprise Server integration. The GitHub Apps-based integration replaces personal OAuth credentials with managed identities, granular repository permissions, and organization-level governance for Heroku delivery workflows. ### Source excerpt Today, we are thrilled to announce the General Availability (GA) of the Heroku GitHub Enterprise Server Integration. For our Enterprise customers, the bridge between code and production must be more than just convenient. It must be resilient, secure, and governed at scale. While our legacy OAuth integration served us well, the modern security landscape demands [...] The post Heroku and GitHub Enterprise Server: Stronger Security, Seamless Delivery appeared first on Heroku. ## Heroku Enters Maintenance Mode, Prompting Migration Planning for Production Applications DevFeed: [Heroku Enters Maintenance Mode, Prompting Migration Planning for Production Applications]() Original publisher: [Read original article]() Author: Wade Wegner Published: 2026-02-09T23:13:29Z Content type: opinion Language: en Sources: [DigitalOcean]() Topics: [Heroku](), [migration](), [Digital Ocean](), [Deployment](), [Databases](), [CI/CD](), [Redis](), [networking]() Tags: [ci-cd](), [community](), [databases](), [deployment](), [digitalocean](), [heroku](), [maintenance](), [migration](), [networking](), [redis]() ### AI overview The article argues that Heroku's shift to a sustaining-engineering model signals maintenance mode and limited future feature investment. It explains that migrating production applications requires planning for data, networking, service dependencies, deployment workflows, workers, scheduled jobs, databases, Redis, CI/CD, environment configuration, DNS, and traffic patterns. ### Source excerpt Heroku's move to a "sustaining engineering" model was carefully worded. It avoids the term end-of-life. It reassures existing customers that nothing changes immediately. It emphasizes stability and support. But if you read between the lines, the message is clear: there is no forward roadmap. There is no new feature investment. The platform is entering maintenance mode. For teams running production systems, the real risk isn't Heroku going offline. It's standing still while the rest of the industry moves forward. Platforms rarely become risky overnight. They become risky when innovation stops. Teams need runtimes that stay current. They need security patches that ship one time. They need platform support for the frameworks and the tooling they're actually adopting. When a platform is no longer investing, those gaps widen over time. Heroku customers may not be panicking, but they are reassessing. And reassessing means confronting a hard truth: code portability may be high, but operational portability is not. Data migration, networking assumptions, service dependencies, and deployment workflows all require planning. The move doesn't have to happen today. But the planning should. "Just Migrate" Is Easy to Say. Harder to Do. Heroku's announcement triggered exactly what you'd expect: a wave of "just migrate to us" messaging from competitors hungry to capture new customers. What most of them leave out is whether their platform can handle the full architecture teams are actually running. Moving in seconds makes for easy marketing, but it's not a serious offer. Engineering teams evaluating their options need a credible path forward, not a marketing pitch. Let's be clear: most Heroku applications are not trivial. They include multiple process types, background workers, scheduled jobs, managed databases, Redis caches, CI/CD pipelines, environment configurations, DNS dependencies, and production traffic patterns. Migration is not just moving a web dyno. It is re-establishing ## An Update on Heroku DevFeed: [An Update on Heroku]() Original publisher: [Read original article]() Author: Nitin T Bhat Published: 2026-02-06T15:19:16Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Security]() Tags: [heroku](), [news](), [operational-excellence](), [platform](), [production](), [security](), [support](), [update]() ### AI overview Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. The platform remains actively supported and production-ready, while product and engineering investments will emphasize quality and operational excellence rather than new features. Existing customers can continue using core services without changes, although Enterprise Account contracts will no longer be offered to new customers. ### Source excerpt Today, Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence rather than introducing new features. We know changes like this can raise questions, and we want to be clear about what this means [...] The post An Update on Heroku appeared first on Heroku. ## Building AI Search on Heroku DevFeed: [Building AI Search on Heroku]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2026-01-29T17:50:08Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [AI search](), [Retrieval-Augmented Generation](), [Claude]() Tags: [ai](), [ai-search](), [building](), [engineering](), [heroku](), [heroku-ai](), [managed-inference-and-agents](), [news](), [pgvector](), [rag](), [retrieval](), [retrieval-augmented-generation](), [search](), [vector-search]() ### AI overview This article presents a Heroku reference architecture for production-grade enterprise AI search using two-stage retrieval. It combines vector search with semantic reranking so documents are scored for whether they answer the query, then uses Claude to generate an answer. ### Source excerpt If you've built a RAG (Retrieval Augmented Generation) system, you've probably hit this wall: your vector search returns 20 documents that are semantically similar to the query, but half of them don't actually answer it. A user asks "how do I handle authentication errors?" and gets back documentation about authentication, errors, and error handling in [...] The post Building AI Search on Heroku appeared first on Heroku. ## Optimize Search Precision with Reranking on Heroku AI DevFeed: [Optimize Search Precision with Reranking on Heroku AI]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2026-01-15T16:00:48Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Inference](), [Retrieval-Augmented Generation](), [model-deployment](), [amazon](), [cohere]() Tags: [ai](), [api](), [availability](), [heroku](), [heroku-ai](), [inference](), [managed-inference-and-agents](), [news](), [rag](), [retrieval-augmented-generation]() ### AI overview Heroku announces general availability of reranking models in Heroku Managed Inference and Agents, with support for Cohere Rerank 3.5 and Amazon Rerank 1.0. The article explains how semantic reranking can improve RAG pipelines by filtering documents for query relevance and reducing noise and token costs. ### Source excerpt Today, we are announcing the general availability of reranking models on Heroku Managed Inference and Agents, featuring support for Cohere Rerank 3.5 and Amazon Rerank 1.0. Semantic reranking models score documents based on their relevance to a specific query. Unlike keyword search or vector similarity, rerank models understand nuanced semantic relationships to identify the most [...] The post Optimize Search Precision with Reranking on Heroku AI appeared first on Heroku. ## Heroku AI: Accelerating AI Development With New Models, Performance Improvements, and Messages API DevFeed: [Heroku AI: Accelerating AI Development With New Models, Performance Improvements, and Messages API]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2025-12-18T19:42:30Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [AI Models](), [API](), [Inference](), [Claude]() Tags: [ai](), [ai-models](), [anthropic](), [api](), [aws](), [claude](), [heroku](), [heroku-ai](), [inference](), [managed-inference-and-agents](), [news]() ### AI overview Heroku announces an expanded Managed Inference and Agents model catalog, including Claude Opus 4.5, Nova 2, Kimi K2 Thinking, MiniMax M2, and Qwen3. The release also describes updated model generations, regional availability, security and data-handling claims, and preview support for Anthropic's Messages API, which aligns with Claude SDKs and enables integration with Claude Code and the Claude Agents SDK. ### Source excerpt This month marks significant expansion for Heroku Managed Inference and Agents, directly accelerating our AI PaaS framework. We're announcing a substantial addition to our model catalog, providing access to leading proprietary AI models such as Claude Opus 4.5, Nova 2, and open-weight models such as Kimi K2 thinking, MiniMax M2, and Qwen3. These resources are [...] The post Heroku AI: Accelerating AI Development With New Models, Performance Improvements, and Messages API appeared first on Heroku. ## Heroku AppLink: Now Using JWT-Based Authorization for Salesforce DevFeed: [Heroku AppLink: Now Using JWT-Based Authorization for Salesforce]() Original publisher: [Read original article]() Author: Vivek Viswanathan Published: 2025-12-11T16:00:53Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [JSON Web Tokens](), [Authorization](), [CI/CD](), [ci](), [Security](), [Microservice](), [OAuth]() Tags: [applink](), [authorization](), [ci-cd](), [continuous-deployment](), [continuous-integration](), [credentials](), [deployment](), [heroku](), [jwt](), [news](), [oauth](), [secrets](), [security](), [tokens]() ### AI overview Heroku AppLink now supports JWT-based authorization for Salesforce integrations. The update enables machine-to-machine authorization for automated CI/CD setup and reduces reliance on long-lived secrets and static credentials by providing on-demand tokens. ### Source excerpt Modern Continuous Integration/Continuous Deployment (CI/CD) pipelines demand machine-to-machine authorization, but traditional web-based flow requires manual steps and often rely on static credentials; a major security risk. Heroku AppLink now uses JWT Authorization to solve both: enabling automated setup and eliminating long-lived secrets. In today's evolving threat landscape, security attacks increasingly exploit systems that rely on [...] The post Heroku AppLink: Now Using JWT-Based Authorization for Salesforce appeared first on Heroku. ## Heroku GitHub Enterprise Integration enters closed pilot with GitHub App-based connections DevFeed: [Heroku GitHub Enterprise Integration enters closed pilot with GitHub App-based connections]() Original publisher: [Read original article]() Author: Alberto Sigismondi Published: 2025-12-10T16:00:09Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [CI/CD](), [Continuous Delivery (CD)](), [GitHub]() Tags: [continuous-delivery](), [continuous-integration](), [credentials](), [deployment](), [heroku](), [heroku-enterprise](), [heroku-pipelines](), [integration](), [news](), [security]() ### AI overview Heroku announces a closed pilot of its GitHub Enterprise Integration for Heroku Enterprise customers. The integration uses a dedicated GitHub App-based service identity instead of personal OAuth tokens to connect GitHub Enterprise Server or Cloud with Heroku deployment pipelines. ### Source excerpt We're excited to announce a significant enhancement to how Heroku Enterprise customers connect their deployment pipelines to GitHub Enterprise Server (GHES) and GitHub Enterprise Cloud (GHEC). The new Heroku GitHub Enterprise Integration is now available in a closed pilot, offering a more secure, robust, and permanent connection between your code repositories and your Heroku apps. [...] The post Heroku GitHub Enterprise Integration: Unlocking Full Continuous Delivery for Enterprise Customers appeared first on Heroku. ## PaaS + IaaS: Heroku and AWS for Cloud-Native Enterprise Agility DevFeed: [PaaS + IaaS: Heroku and AWS for Cloud-Native Enterprise Agility]() Original publisher: [Read original article]() Author: Gillian Gual Hinkle Published: 2025-12-04T19:50:28Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Amazon Web Services](), [Platform as a Service (PaaS)](), [Infrastructure as a Service (IaaS)](), [Cloud](), [Development]() Tags: [applications](), [aws](), [cloud](), [cloud-infrastructure](), [cloud-native](), [deploy](), [development](), [engineering](), [heroku](), [heroku-enterprise](), [infrastructure-as-a-service-iaas](), [maintenance](), [platform-as-a-service-paas](), [providers](), [scale](), [services](), [velocity]() ### AI overview The article explains how enterprises can combine Heroku's managed PaaS with AWS infrastructure to build and operate cloud-native applications. It highlights reduced operational burden, greater developer focus, and a Salesforce example involving applications used by more than 76,000 employees. ### Source excerpt For modern enterprises building cloud-native applications, success hinges on achieving maximum development velocity at every scale. Infrastructure as a Service (IaaS) providers like AWS provide hundreds of services with the unmatched reliability and scale needed for enterprise infrastructure, but they can require significant effort and expertise for organizations to be effective and efficient. To achieve [...] The post PaaS + IaaS: Heroku and AWS for Cloud-Native Enterprise Agility appeared first on Heroku. [Next page]()