Private corporate batches, live online cohorts and 1-on-1 mentoring in JFrog Artifactory — checksum-based binary storage, build integration, high availability and multi-site replication — 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 Artifactory as tier-one infrastructure, not a file server — local, remote and virtual repository design, checksum-based storage and what it means for copies, moves and disk sizing, filestore configuration against local disk and object storage, and BuildInfo-driven promotion from a CI build through to a release repository. Sessions cover the operational depth teams book for: security and permission targets, reverse proxy and Docker registry configuration, YAML configuration files, REST API automation, backups, import and export, log analytics and JMX metrics, high-availability cluster setup, migration off shared NFS, and honest coverage of what Pro, Enterprise Plus, Edge and Access Federation each unlock.
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 Artifactory that means a trainer who has run it in production — JFrog Artifactory — checksum-based binary storage, build integration, high availability and multi-site replication — 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 Artifactory batchArtifactory is JFrog's binary repository manager — the system of record for every binary an organisation produces and consumes. It presents local repositories for what you publish, remote repositories that proxy and cache external registries, and virtual repositories that aggregate both behind a single resolution URL, across more than thirty package types including Maven, Gradle, Docker, npm, NuGet, PyPI, Go, Debian, RPM, Conan and Helm.
What separates Artifactory architecturally is how it stores things. The filestore is checksum-based: every binary is written once under its SHA checksum and the repository layout is metadata pointing at it. Ten repositories holding the same JAR hold one copy on disk, a copy operation is a metadata write rather than a byte copy, and integrity is verifiable by construction. The filestore itself can be a local disk, a mounted volume, or object storage such as S3 or GCS, configured independently of the database that holds the metadata.
The second differentiator is build integration. Artifactory captures BuildInfo — the modules produced, the dependencies resolved, the environment and the CI job that produced them — and stores it alongside the artifacts. That turns questions like which build produced this image, what went into it, and has this exact artifact been promoted to production into queries rather than archaeology. On top of that sit the enterprise capabilities teams eventually need: active-active high availability, replication between sites, Edge nodes for distribution, and Access Federation so identity is consistent across a multi-instance estate.
Binaries became the unit of delivery. Containers, packages and charts are what actually reach production, and the questions asked about them are now compliance questions: what is inside this image, which build produced it, was it promoted or rebuilt, and can you prove that. A repository that only stores files cannot answer those. One that records build metadata alongside them can.
That is why Artifactory shows up in regulated and large-scale environments in particular. The capabilities organisations buy it for — active-active high availability, cross-site replication, Edge distribution, checksum-based storage against object stores, and a consistent identity model across instances — are the ones that only matter once a repository is genuinely load-bearing. When the artifact store goes down, every build in the company stops, so it gets treated as tier-one infrastructure.
The skills gap sits exactly there. Plenty of engineers can create a repository through the UI. Far fewer can size a filestore, move it to object storage without downtime, design a promotion pipeline driven by BuildInfo, stand up an HA cluster, migrate off shared NFS, or restore an instance under pressure. That operational half is what a private batch is usually booked for.
What a binary repository manager is for, and why the answer changed once containers and supply-chain questions arrived. Artifactory's terminology and repository types, and the position it occupies relative to other repository managers — including where a simpler tool would serve you better.
Topics: Artifactory overview · The role of Artifactory in a DevOps toolchain · Artifactory terminology · Repository types: local, remote, virtual, federated and distribution · Package types and what native support actually means · Where Artifactory is more than a team needs
Getting a working instance on the shapes teams actually deploy: Linux from an archive or package, Windows, and containers. Then the upgrade path, because an Artifactory instance lives for years and the upgrade is the operation that scares people most.
Topics: System requirements and sizing · Installing Artifactory on Linux · Installing on Windows · Installing with Docker and Docker Compose · First-time setup and licence activation · Upgrading Artifactory across versions · Service management, ports and start-up troubleshooting
The working surface: browsing the repository tree, viewing packages with their native metadata, searching by name, checksum, property and AQL, and manipulating artifacts through copy, move, delete and properties — where checksum-based storage makes operations that look expensive almost free.
Topics: Getting started and general navigation · Browsing Artifactory and the tree view · Viewing packages and native package metadata · Searching for artifacts: quick, package, checksum and property search · Artifactory Query Language basics · Manipulating artifacts: copy, move, delete, properties · Updating your user profile and generating credentials · Deploying through WebDAV
Connecting the builds. Deploying and resolving with Maven through virtual repositories, exposing Maven indexes, then the container path: setting up a Docker registry, choosing between subdomain, port and path-based access, and putting a reverse proxy in front of it correctly.
Topics: Deploying artifacts using Maven · Downloading and resolving artifacts using Maven · settings.xml, virtual repositories and distributionManagement · Exposing Maven indexes · Setting up a Docker registry in Artifactory · Docker access methods: subdomain, port and repository path · Configuring a reverse proxy for Docker and web access · Snapshot handling and deploying to a public OSS snapshot repository
The configuration that determines cost, performance and durability. How metadata in the database and bytes in the filestore are separated, what checksum-based storage means for deduplication, and how to configure a filestore against local disk, a mounted volume or object storage. Then repository configuration in depth.
Topics: Configuring the database and supported engines · Configuring the filestore · Checksum-based storage and deduplication · Object storage backends including S3 · Configuring repositories: local, remote and virtual · Remote repository caching, offline mode and retrieval policies · Configuration files and their precedence · YAML configuration files and configuration as code · Mail server configuration and IPv6 support
Who can read, deploy, promote and delete — expressed through permission targets rather than ad-hoc grants. Authentication options including directory integration, credential types that belong in CI, and the identity model that keeps a multi-instance estate consistent.
Topics: Artifactory authentication options · Configuring security and realms · Users, groups and permission targets · Include and exclude patterns within a permission target · Access tokens versus API keys versus passwords · Credentials in CI pipelines · Access Federation across instances · Anonymous access and the decisions it forces
The capability that distinguishes Artifactory from a file store. Publishing BuildInfo from a CI job so the artifacts, the dependencies that went into them, and the environment that produced them are recorded together — then using that record to promote a build rather than rebuild it.
Topics: What BuildInfo captures and why it matters · Publishing build information from CI · The JFrog CLI and build-scoped commands · Build browsing, comparison and diff · Promotion between repositories using build metadata · Build retention and cleanup · Tracing an artifact back to the build that produced it
Treating Artifactory as programmable infrastructure. Repository, user and permission provisioning through the API, artifact deployment and retrieval, property-driven workflows, and the queries that let you answer storage and usage questions without opening the interface.
Topics: Artifactory REST API structure and authentication · Provisioning repositories, users and permissions via API · Deploying and retrieving artifacts programmatically · Properties, property-based search and AQL over the API · Storage and usage reporting through the API · Scripting routine administration · Rate limits, error handling and idempotent automation
Keeping a tier-one service healthy. What the system information page tells you, which log files to read and in what order, the JMX metrics worth alerting on, and the maintenance operations that keep storage bounded. Then backup, import and export, and the restore that proves any of it worked.
Topics: System monitoring and system information · Artifactory log files and what each one records · JMX MBeans and metrics worth alerting on · Log analytics and shipping logs to an external stack · Regular maintenance operations: garbage collection, storage cleanup, index rebuild · Managing backups · Importing and exporting system and repository data · Managing disk space usage · Troubleshooting a slow or unresponsive instance
Running Artifactory so that a node failure is not a company-wide build outage. Cluster architecture, installation and setup, the shared storage question, day-to-day cluster management, migrating off NFS to object storage, and diagnosing the failure modes specific to a clustered deployment.
Topics: Artifactory high availability architecture · HA installation and setup · Load balancer configuration and session handling · Managing the HA cluster and rolling upgrades · Shared storage options and their trade-offs · Migrating data from NFS to object storage · Troubleshooting HA: split behaviour, node desync, licence issues · Clustering and capacity planning
What you get for what you pay, stated plainly. The capability boundaries between OSS, Pro, Enterprise and Enterprise Plus, distribution repositories and Edge nodes for pushing releases to remote sites, Access Federation across an estate, and a structured approach to troubleshooting when something in this stack misbehaves.
Topics: Artifactory Pro capabilities · Artifactory Enterprise and Enterprise Plus · Artifactory Edge and release distribution · Distribution repositories and signed release bundles · Access Federation across instances · Replication: push, pull, event-based and scheduled · Structured troubleshooting across the platform · Choosing an edition against a real requirement list
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild a repository topology for a polyglot application, point every build at virtual repositories, then restructure the members behind them with no build changes.
Take a populated instance on local disk, reconfigure the filestore against S3-compatible storage, and verify checksum integrity and resolution afterwards.
Publish BuildInfo from a CI job, inspect the captured dependencies and environment, then promote the same binary from staging to release and trace it back.
Configure Artifactory as a Docker registry, choose an access method, put a TLS reverse proxy in front, and debug the URL and authentication failures that follow.
Stand up an HA pair behind a load balancer, kill a node under load, then perform a rolling upgrade without interrupting builds.
Back up system configuration and repository data, destroy the instance, restore it, and verify that every published artifact and every build record survived.
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
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.
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
| 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 advisorDelivered onsite at your premises or live online in your timezone.
Prefer to call or email?
More ways to reach us on the contact page.