Skip to main content
​
March 3, 2026

​
Realtime run status of services

We released a major new enhancement to services today. You can now see the realtime status of all services running within each environment, without having to use LocalOps CLI or Kubectl CLI.service run statusDepending on the service type, status text will be different. Here are the possible status texts:For example, for web, internal services and worker services, you will see the following statuses:
  • running (2/2)
  • degraded (1/2)
  • failing (0/2)
  • stopped
(x/y) format shows the number of replicas running (x) out of total number of replicas (y).For job services:
  • pending
  • succeeded
  • failed
  • timeout
For cronjob services:
  • idle
  • active
  • suspended
You can see them in service tile view or within service section at the top of the page.

​
New “Runs” tab

Lookout for the new “Runs” tab for job and cronjob services. You can see the run history and status of each run.We update statuses in near real time so you would know when you service is failing, just by looking at the status text in LocalOps console.All of these changes were made to make it easier for you to monitor and manage your services, without having to drop into shell or CLI.
​
Feb 27, 2026

​
New feature: Custom Node groups

So far, environments have been having a single node group created, to run all the services.Now, you can create multiple node groups to run different types of services. For each node group you can pick
  1. AMIs
  2. Instance types
  3. Desired count of nodes
list node groupsGo to the new Node groups section to create and manage node groups.You can now create
  1. Windows node groups to run windows based services (or)
  2. Linux node groups to run linux base services
And while creating a service or updating a service, you can assign it to any one of the node groups. And all its replicas or containers will run in configured nodes.

​
Spot instances

In the case of AWS evnironments, while creating node groups, you can pick between ON_DEMAND or SPOT as capacity types.So you can create node groups of SPOT instance type and assign interruptible and idempotent services like jobs, crons, batch processing, or other. This will end up giving up to 50% savings in compute costs.
​
Feb 9, 2026

​
New feature: Deployment notes

While triggering new deployments, you can now pass a note text to it. And it will communicate to rest of the team about what the deployment is all about.We made other QoS updates here to ensure smooth execution of deployment pipelines.
​
Feb 7, 2026

​
New feature: Account level resource tags

All cloud resources of all environments spinned by LocalOps are attached with two standard tags. One with ID of the environment and another with name of the environment. These tags can be used in Cost explorer to analyse costs at a granular level.We released a new feature today to accept custom tags so that you can assign your own key value pairs as tags for all resources spinned up in all environments of the account. You can use it to attach tags like:
  1. bu: internal
  2. bu: product-1
  3. project: project-name
Go to Account settings > Resource tags to start adding custom tags.
​
Jan 13, 2026

​
Bring your own registry

LocalOps can now use your images from your own docker registry to deploy services in your environments. Go to the new Registries section to add any private docker registry.We support ECR & DockerHub as of today and plan to support other providers in the coming weeks.
  1. Amazon Elastic Container Registry (ECR)
  2. DockerHub
  3. Google container registry
  4. Azure container registry
  5. Github packages
(Talk to us if you need us to support any other registry).

​
Bring your code pipeline

​
Deploy using LocalOps API

You can run your exisitng code build pipelines to build code and finally call LocalOps API to deploy the code to your environment. Checkout the API reference for the new /deploy api here.Eg.,
curl --request POST \
  --url https://sdk.localops.co/v1/environments/{envId}/services/{serviceId}/deploy \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "docker_image_tag": "a1b2c3d4"
}
'

​
🍦 Deploy using LocalOps Github action

To cut work, you can also embed our Github action step directly within your .github/workflows/deploy.yml to trigger new deployments.Like:
- use: localopsco/deploy-action
  with:
    - service: auf-d0923-8rljks-fd9o8
    - environment: afdsfk-j092309-4laskd-jf32
    - token: aslkjadsf-dkjfie-uriw-skjf-19823r
    - docker_image_tag: 1.2.2
You can pass docker_image_tag or commit_id or helm_chart_version to the action to trigger new deployments.or with commit sha like:
- use: localopsco/deploy-action
  with:
    - service: auf-d0923-8rljks-fd9o8
    - environment: afdsfk-j092309-4laskd-jf32
    - token: aslkjadsf-dkjfie-uriw-skjf-19823r
    - commit_id: akf9a0sd98

​
Pass ops.json as configuration

For Docker-image based services, you can now add ops.json as configuration to the service settings within LocalOps console. This will work as documented in ops.json configuration here.
For the previous year, check out 2025