SRE Conf 2023
Rootconf For members

SRE Conf 2023

Availability and reliability 24/7- the SRE life



Schedule for the conference on 24 November is published.

Why SRE Conf?

When any organization goes from product market fit or beta test phase to production rollout, or from first x customers to 10x or 100x customers and starts scaling, they typically start running into challenges with systems stability and resiliency. These challenges change with every phase of growth. So does the need for having a SRE team and/or a DevOps team, and the role these teams play.
Unfortunately, there is no one-size-fits-all solution when it comes to what roles these teams should play, and which tools various teams should use to track the metrics and processes involved. But there are some common building blocks that apply in similar (and different) ways and forms for most teams. The idea of the SRE Conference is to get together and to know about these building blocks, share and learn about the themes that fall under the SRE umbrella.

SRE Conf tracks

SRE Conf is a two-track conference. The track, “Culture, career and Evolution” is more focused on leadership, team, and organizational topics while the “Stories from the Trenches” track will cover real-world scenarios, and lessons learned which will help engineers and engineering teams to upskill themselves by understanding experiences from their industry peers.

Culture, career, and evolution

  1. SRE v/s DevOps v/s Platform Engineering teams in organizations.
  2. Hiring and building SRE teams.
  3. Blameless postmortems.
  4. Role of AI in SRE/DevOps/Platforms.
  5. FinOps and cost optimization.
  6. SRE Anti-patterns

Stories from the trenches:

  1. Incident management.
  2. Change management.
  3. Scalability and performance.
  4. SLA/SLO and golden signals.
  5. Security and DevSecOps.
  6. Systems and networking.

Key takeaways for participants

  1. Improved understanding of organizational needs and requirements.
  2. Enhanced optimization skills.
  3. Networking opportunities.
  4. Knowledge sharing and community building.

Who should participate

  • Members of SRE, DevOps or platform teams.
  • A software developer or manager who is responsible for services running on any cloud platform or on-prem data center.
  • Technology leader of an engineering team that manages critical systems which should have minimal to zero downtime.


If you are interested in speaking at the conference, submit your talk idea here. The editors - Sarika Atri, Safeer CM and Saurabh Hirani - will review your talk description and give feedback.

Speakers will also receive feedback and assistance during rehearsals from past speakers such as Sitaram Shelke.

Guidelines for speaking, speaker honorarium policy, and travel grant policy details are published here.

About the editors

This conference themes were set up by Sarika Atri and Safeer CM. Together with Saurabh Hirani, the three editors have:

  1. Reviewed the talks.
  2. Set up the editorial workflow.
  3. Finalized talk selections.
  4. Curated the schedule.

Sarika Atri is Software Architect with over twenty years experience in the industry. Sarika was reviewer for Rootconf Cloud Costs Optimization conference held in July 2023.
Safeer CM is Senior Staff SRE at Flipkart. He is author of Architecting Cloud-Native Serverless Solutions published by Packt.
Saurabh Hirani is former editor of Rootconf, and a passionate member of the community. Saurabh is SRE at,. He has a keen interest in mentoring speakers.

Become a Rootconf Member to join

SRE Conf is a community-funded conference. It will be held in-person. Attendance is open to Rootconf members only. Support this conference with a membership. If you have questions about participation, post a comment here.


Sponsorship slots are open for:

  1. Tool and solutions providers.
  2. Companies interested in tech branding for hiring.

Email sponsorship queries to

Contact information

Join the Rootconf Telegram group at or follow @rootconf on Twitter.
For inquiries, contact Rootconf at +91-7676332020.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more
Sreeram Venkitesh

Sreeram Venkitesh


Scaling neetoDeploy from zero to production - Building, maintaining and optimizing our cloud deployment platform

Submitted Oct 27, 2023

At BigBinary, we’ve been building neetoDeploy for the past one year.

We were running all our PR review apps across around 25-30 projects on Heroku. Last year once Heroku announced that they’re getting rid of their free plans, we started off by building a platform to deploy PR review apps. We kept the date Heroku was planning to remove their free plans as a deadline and quickly put together our platform on top of Kubernetes so that we could migrate all our apps from Heroku. We completed this way before the deadline and spent the rest of the time fixing bugs and stabilizing the platform. We architected an entire idle mechanism for the apps, based on the network requests each service recieves. If an app is not accessed for 5 minutes, it will get scaled down and would only be brought back up when its accessed again. We were able to bring down our costs substantially with this.

Once we had nailed PR review apps, we started experimenting with staging and production app deployments. Since the basic functionality was there, we were able to bring it together easily. With this, we moved all of BigBinary’s internal staging deployments to neetoDeploy. One of the major uses of staging deployments was to run Cypress tests against them everyday.

After we started using our platform to deploy staging apps, we started facing a lot of stability issues with existing features. We had to rebuild and re-architecture several features that we had already implemented, kind of like building the Ship of Theseus. We went back to the drawing board and designed a new efficient way of streaming logs faster. We setup cluster autoscaler to handle load, and overprovisioned the cluster ever so lightly based on the existing deployments, so that new deployments never have to wait for the cluster to be up, resulting in seamless and fast deployments. We moved from an external docker registry to our own registry hosted inside our Kubernetes cluster to bring down network costs and latency and so on.

The last one year has been a rollercoaster ride in terms of learning and experimenting. Working on and maintaining neetoDeploy over the past year taught me a lot of lessons the hard way and I’ve understood what SRE means in a project of this scale. We wrote a bunch of blog posts about it too.

This is the neetoDeploy story - how we built a cloud deployment platform as a service from scratch and took it to production in a year.


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more