Private corporate batches, live online cohorts and 1-on-1 mentoring in browser-based developer workspaces — containerised runtimes, stacks and factories, multi-server installation, LDAP identity, scaling and disaster recovery — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches Codenvy from the operator's side as well as the developer's: workspace and environment definitions, project types and commands, factories and badged repositories for one-click contribution, then multi-server installation, Docker configuration, LDAP-backed authentication, permissions and the CLI and API that let all of it be automated. Sessions concentrate on what determines whether a workspace platform survives real use — image and stack governance, storage and networking behaviour when a whole team starts workspaces at once, monitoring, scaling, backup and a rehearsed disaster recovery path — and the concepts are mapped explicitly onto Eclipse Che and OpenShift Dev Spaces so the knowledge outlives the specific distribution.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Codenvy that means a trainer who has run it in production — browser-based developer workspaces — containerised runtimes, stacks and factories, multi-server installation, LDAP identity, scaling and disaster recovery — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Codenvy batchCodenvy is a cloud development environment platform: instead of every engineer configuring a toolchain on a laptop, a workspace is defined once as code, provisioned as containers on shared infrastructure, and opened in a browser. The workspace carries the runtime, the build tools, the source and the commands that build, run and preview the project, so a new joiner or a contractor becomes productive in minutes rather than in days of environment archaeology.
The building blocks are consistent throughout. An environment is a set of containerised machines with declared memory and image; a project is source plus the metadata describing its type; commands are named build, run, debug and preview actions bound to the workspace; and a factory is a shareable URL that materialises a fully configured workspace from a repository, optionally badged directly in the repository so a contributor can start work without cloning anything. Stacks cover the usual runtimes — Java JAR, WAR and Spring, Maven multi-module, JavaScript and Node.js, Python, PHP, Ruby on Rails and Android.
Codenvy has a lineage worth being explicit about, because it decides what a team should invest in. It is the commercial distribution of Eclipse Che, and after the technology moved to Red Hat it continued as CodeReady Workspaces and then as OpenShift Dev Spaces. Installations of Codenvy itself are still in service inside enterprises, and the architecture, administration and operations knowledge transfers almost directly to Che and Dev Spaces — which is how this course treats it.
Local development environments have become the most expensive unmanaged dependency most engineering organisations own. A modern service needs a specific language runtime, a container engine, a database, a message broker, cloud credentials and half a dozen CLI tools, and every laptop drifts from every other one. The result is a category of defect that only reproduces on one machine, and an onboarding cost measured in days.
Cloud development environments answer that by making the environment a versioned artefact rather than a local accident. The same argument that moved builds onto CI servers applies to development: reproducibility, faster onboarding, and the ability to grant and revoke access rather than trusting a laptop with source code. For regulated organisations and for contractor-heavy teams, keeping the code inside infrastructure you control is often the deciding factor rather than a convenience.
Codenvy sits at the origin of that category, and the operational questions it raises are the same ones every current platform raises: how workspaces are declared, how runtime images are governed, how identity integrates with the corporate directory, how storage and networking behave when hundreds of workspaces start on a Monday morning, and what disaster recovery means when developer state lives on shared infrastructure. Those are the skills that transfer, whichever product a team ends up standardising on.
What problem a workspace platform solves and how Codenvy solves it. The architecture from browser to container — workspace, environment, machine, project, command — the role of Docker underneath, and an honest map of the lineage through Eclipse Che, CodeReady Workspaces and OpenShift Dev Spaces so teams know what transfers.
Topics: The local environment problem and what reproducibility buys · Codenvy architecture: server, workspace master and workspace agents · Workspaces, environments and machines · Projects, project types and metadata · Commands and the workspace lifecycle · Docker as the runtime substrate · Lineage: Codenvy, Eclipse Che, CodeReady Workspaces, OpenShift Dev Spaces · Getting started: first workspace end to end
Standing the platform up and keeping it current. Single-server installation, the Vagrant route for evaluation, multi-server topology for real use, cloud marketplace deployment, then Docker configuration, licensing and the upgrade path — plus the installation failures that account for most first-day support tickets.
Topics: Installation prerequisites and sizing · Single-server installation · Installation with Vagrant for evaluation · Multi-server installation and topology · Cloud marketplace deployment, including Azure · Installation troubleshooting: ports, Docker, storage and DNS · Configuration files and configuration precedence · Docker configuration: daemon, storage driver and registries · Licensing and license management · Upgrading between versions safely
The developer-facing model in depth. Defining environments with the right images and memory, importing projects from Git and other sources, project types and their effect on tooling, and templates that let a team start a new service with the environment already correct.
Topics: Environment definitions: images, machines and memory allocation · Custom runtime images and image governance · Creating and importing projects · Import sources: Git, ZIP archive and existing workspaces · Project types and language tooling · Templates and stack definitions · Workspace configuration as code · Workspace lifecycle: start, stop, snapshot and reclaim
Making the workspace do the work. Command definitions and macros, build and run commands wired to the project's real toolchain, preview URLs and port exposure, and debugging inside a containerised workspace rather than on a laptop.
Topics: Command types and command definitions · Build commands and toolchain invocation · Run commands, processes and process output · Preview URLs and server port exposure · Macros and workspace variables · Debugging inside a workspace · Terminal access and shell workflow · Command sharing across a team
The stacks teams actually use, and what each one needs to work properly. Java in its several shapes, JavaScript and Node.js, Python, PHP, Ruby on Rails and Android — with dependency caching, multi-module builds and the mistakes that make a stack unusably slow.
Topics: Java JAR, WAR and application server workflows · Java Spring projects and application configuration · Maven multi-module projects and reactor builds · JavaScript and Node.js workspaces · Python workspaces and virtual environments · PHP workspaces and web server configuration · Ruby on Rails workspaces · Android build workflows in a container · Dependency caching and build performance · Choosing and extending a stack
The workspace as part of the delivery pipeline rather than an island. Git and SVN integration, issue management and CI links, factories that materialise a configured workspace from a URL, badged repositories for one-click contribution, guided tours for onboarding, and desktop IDE access for people who want it.
Topics: Git integration: clone, branch, commit, push and credentials · SVN and other version control support · Issue management integration · Continuous integration from the workspace · Factories: creating, configuring and sharing · Badged repositories for one-click contribution · Custom guided tours for onboarding · Using desktop IDEs against a remote workspace · A DevOps workflow built around ephemeral workspaces
Running the platform for an organisation. Authentication and LDAP integration, user and team management, the permission model across workspaces and organisations, email and notification configuration, and the security posture of a system that holds source code and credentials.
Topics: Administration overview and the admin surface · Authentication mechanisms and session handling · LDAP and directory integration · User management, onboarding and deprovisioning · Teams, organisations and resource allocation · Permissions model and role assignment · Email and notification configuration · Security: secrets, credentials and workspace isolation · Audit and access review
Keeping it running when a hundred engineers start workspaces at nine in the morning. Networking and ingress, monitoring and capacity signals, horizontal scaling, backup of the data that actually matters, disaster recovery rehearsed rather than documented, and automating all of it through the CLI and API.
Topics: Networking, ingress, DNS and TLS · Monitoring: platform metrics, workspace metrics and capacity signals · Scaling the workspace master and node capacity · Storage layout, volumes and reclamation · Backup: what to back up and how often · Disaster recovery planning and rehearsal · Operational runbook for common failures · The Codenvy CLI for administration · The REST API and automating platform operations
We rebuild the agenda around the tools you actually run.
Request a custom agendaInstall Codenvy on one host, break it deliberately on ports, storage and Docker configuration, fix each failure, then rebuild it as a multi-server topology.
Define an environment, custom image, project type and full command set for one of your own repositories, then hand it to a colleague and see if it starts clean.
Bring up Java Maven multi-module, Node.js and Python stacks with working dependency caching, and measure cold versus warm build time for each.
Publish a factory, badge the repository, add a guided tour, and time how long a genuinely new contributor takes to reach a passing build.
Integrate authentication with a directory, map groups to teams and permissions, then run through onboarding, role change and deprovisioning for a test user.
Load the platform with concurrent workspace starts, watch the capacity signals, scale it, then perform a backup and a full disaster recovery restore against the clock.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.