CPA Tech Wiki - User contributions [en]

Podcast

2026-09-01T01:50:11Z

Bftcpa606: /* Episode List (2025-Present, episodes 187-) */

[[File:Podcast 1080p.webp|thumb|300x300px|ATL Logo used by CPA Practice Advisor, 20260324]]

= Accounting Technology Lab Podcast =

'''Accounting Technology Lab''' is a weekly podcast hosted by Randy Johnston and Brian F. Tankersley, CPA, focusing on the intersection of accounting, audit, tax, and technology. It is published by '''CPA Practice Advisor''' and covers trends in accounting software, AI/automation, audit innovation, advisory models, and more. The podcast presents interviews, reviews of new tools, case studies, and commentary on how technology is reshaping public accounting.

The podcast is distributed [https://www.cpapracticeadvisor.com/series/accounting-technology-lab-podcast/ HERE] by CPA Practice Advisor as part of the CPA Practice Advisor's weekly [https://www.cpapracticeadvisor.com/section/technology/ technology] newsletter at the end of each week, and is also published to [https://www.youtube.com/@AccountingTechnologyLab YouTube (@AccountingTechnologyLab]). The new episodes premiere on YouTube at noon ET each Friday.

You can also see a list of Wiki articles for each episode at [[ATL Podcast Episodes by Year|the Episodes by Year page]].

== Episode List (2025-Present, episodes 187-) ==
{| class="wikitable sortable"
|+
! Ep# !! Title !! CPAPA Link !! Record Date !! Publish Date
|-
|[https://cpate.ch/273 273]
|[[ATL273|Reinventing Your Practice with Advisory (Guest: Nancy Sperry, Sage)]]
|[https://cpate.ch/atl273pub atl273pub]
|8/7/2026
|8/28/2026
|-
|[https://cpate.ch/272 272]
|[[ATL272|The Gathering Storm: Open Source AI]]
|[https://cpate.ch/atl272pub atl272pub]
|8/7/2026
|8/28/2026
|-
|[https://cpate.ch/271 271]
|[[ATL271|Why Your WISP Is Essential in 2026]]
|[https://cpate.ch/atl271pub atl271pub]
|8/7/2026
|8/21/2026
|-
|[https://cpate.ch/270 270]
|[[ATL270|Hardware Hullabaloo]]
|[https://cpate.ch/atl270pub atl270pub]
|7/2/2026
|8/14/2026
|-
|[https://cpate.ch/269 269]
|[[ATL269|Microsoft Agent 365]]
|[https://cpate.ch/atl269pub atl269pub]
|7/2/2026
|8/7/2026
|-
| [https://cpate.ch/268 268] || [[ATL268|Scaling New Heights 2026 (Part Two)]] || [https://cpate.ch/atl268pub atl268pub] || 7/2/2026 || 7/30/2026
|-
| [https://cpate.ch/267 267] || [[ATL267|AI is the Ultimate Accounting Assistant (Part Two)]] || [https://cpate.ch/atl267pub atl267pub] || 7/2/2026 || 7/23/2026
|-
| [https://cpate.ch/266 266] || [[ATL266|AI is the Ultimate Accounting Assistant, with guest Sasha Orloff of Puzzle.io]] || [https://cpate.ch/atl266pub atl266pub] || 7/2/2026 || 7/16/2026
|-
| [https://cpate.ch/265 265] || [[ATL265|Scaling New Heights 2026 - "Strange New World"]] || [https://cpate.ch/atl265pub atl265pub] || 6/15/2026 || 7/10/2026
|-
| [https://cpate.ch/264 264] || [[ATL264|AICPA ENGAGE 2026 and CPAPA Thought Leader/40 Under 40 Mashup]] || [https://cpate.ch/atl264pub atl264pub] || 6/15/2026 || 7/3/2026
|-
| [https://cpate.ch/263 263] || [[ATL263|Why General AI is Not Suitable For Tax Research With Guest Kashif Ali - Founder, TaxGPT]] || [https://cpate.ch/atl263pub atl263pub] || 6/5/2026 || 6/20/2026
|-
| [https://cpate.ch/262 262] || [[ATL262|2026 Black Ore AI Tax Summit]] || [https://cpate.ch/atl262pub atl262pub] || 6/5/2026 || 6/13/2026
|-
| [https://cpate.ch/261 261] || [[ATL261|Keyveve]] || [https://cpate.ch/atl261pub atl261pub] || 5/1/2026 || 6/5/2026
|-
| [https://cpate.ch/260 260] || [[ATL260|Next Generation Document Management]] || [https://cpate.ch/atl260pub atl260pub] || 5/1/2026 || 5/29/2026
|-
| [https://cpate.ch/259 259] || [[ATL259|The Dead Pool]] || [https://cpate.ch/atl259pub atl259pub] || 5/1/2026 || 5/22/2026
|-
| [https://cpate.ch/258 258] || [[ATL258|Recruiting the Next Generation]] || [https://cpate.ch/atl258pub atl258pub] || 5/1/2026 || 5/15/2026
|-
| [https://cpate.ch/257 257] || [[ATL257|Mythos: The AI Strikes Back]] || [https://cpate.ch/atl257pub atl257pub] || 5/1/2026 || 5/8/2026
|-
| [https://cpate.ch/256 256] || [[ATL256|Suite vs. Best In Breed]] || [https://cpate.ch/atl256pub atl256pub] || 4/3/2026 || 5/1/2026
|-
| [https://cpate.ch/255 255] || [[ATL255|Generative AI in (Your) Practice]] || [https://cpate.ch/atl255pub atl255pub] || 4/3/2026 || 4/24/2026
|-
| [https://cpate.ch/254 254] || [[ATL254|Decision Intelligence with guest Eric Eager of 4ImpactData]] || [https://cpate.ch/atl254pub atl254pub] || 4/3/2026 || 4/17/2026
|-
| [https://cpate.ch/253 253] || [[ATL253|2026 CPA Practice Advisor Thought Leader Symposium]] || [https://cpate.ch/atl253pub atl253pub] || 4/3/2026 || 4/10/2026
|-
| [https://cpate.ch/252 252] || [[ATL252|The Future of AI in 2026 Accounting Technology (Joe Woodard, guest)]] || [https://cpate.ch/atl252pub atl252pub] || 3/6/2026 || 4/3/2026
|-
| [https://cpate.ch/251 251] || [[ATL251|The Real State of Accounting Tech in 2026 (Joe Woodard, guest)]] || [https://cpate.ch/atl251pub atl251pub] || 3/6/2026 || 3/27/2026
|-
| [https://cpate.ch/250 250] || [[ATL250|AICPA Startup Accelerator - 2026 Cohort]] || [https://cpate.ch/atl250pub atl250pub] || 3/6/2026 || 3/20/2026
|-
| [https://cpate.ch/249 249] || [[ATL249|Zoho Day 2026]] || [https://cpate.ch/atl249pub atl249pub] || 3/6/2026 || 3/13/2026
|-
| [https://cpate.ch/248 248] || [[ATL248|Analysis with ChatGPT Pro 5]] || [https://cpate.ch/atl248pub atl248pub] || 11/10/2025 || 3/6/2026
|-
| [https://cpate.ch/247 247] || [[ATL247|Vibe Coding with AI]] || [https://cpate.ch/atl247pub atl247pub] || 11/10/2025 || 2/27/2026
|-
| [https://cpate.ch/246 246] || [[ATL246|Model Context Protocol]] || [https://cpate.ch/atl246pub atl246pub] || 2/6/2026 || 2/20/2026
|-
| [https://cpate.ch/245 245] || [[ATL245|ATL 245 – The Future of AI and Agents in Accounting]] || [https://cpate.ch/atl245pub atl245pub] || 2/6/2026 || 2/13/2026
|-
| [https://cpate.ch/244 244] || [[ATL244|Acumatica Summit 2026]] || [https://cpate.ch/atl244pub atl244pub] || 2/6/2026 || 2/6/2026
|-
| [https://cpate.ch/243 243] || [[ATL243|AI Trends at CES 2026 – Part 3]] || [https://cpate.ch/atl243pub atl243pub] || 1/8/2026 || 1/30/2026
|-
| [https://cpate.ch/242 242] || [[ATL242|More from CES 2026 - Part 2]] || [https://cpate.ch/atl242pub atl242pub] || 1/8/2026 || 1/23/2026
|-
| [https://cpate.ch/241 241] || [[ATL241|CES 2026: Key Trends and Observations]] || [https://cpate.ch/atl241pub atl241pub] || 1/8/2026 || 1/16/2026
|-
| [https://cpate.ch/240 240] || [[ATL240|Nick Chandly, Founder/CEO, Forwardly #ATL240]] || [https://cpate.ch/atl240pub atl240pub] || 12/12/2025 || 1/9/2026
|-
| [https://cpate.ch/239 239] || [[ATL239|Jeff Seibert, Founder/CEO, Digits #ATL239]] || [https://cpate.ch/atl239pub atl239pub] || 12/4/2025 || 1/2/2026
|-
| [https://cpate.ch/238 238] || [[ATL238|Selecting the Right AI Partner with Wiss #ATL238]] || [https://cpate.ch/atl238pub atl238pub] || 12/4/2025 || 12/29/2025
|-
| [https://cpate.ch/237 237] || [[ATL237|Thomson Reuters Synergy Executive Roundtable]] || [https://cpate.ch/atl237pub atl237pub] || 11/7/2025 || 12/19/2025
|-
| [https://cpate.ch/236 236] || [[ATL236|Intuit QBD Pricing, Open AI Relationship]] || [https://cpate.ch/atl236pub atl236pub] || 12/4/2025 || 12/12/2025
|-
| [https://cpate.ch/235 235] || [[ATL235|2025 Thomson Reuters Synergy]] || [https://cpate.ch/atl235pub atl235pub] || 11/10/2025 || 12/5/2025
|-
| [https://cpate.ch/234 234] || [[ATL234|2025 CCH User Conference]] || [https://cpate.ch/atl234pub atl234pub] || 11/10/2025 || 11/28/2025
|-
| [https://cpate.ch/233 233] || [[ATL233|2025 CPAPA Tech Innovation Awards (Part 2/2)]] || [https://cpate.ch/atl233pub atl233pub] || 10/3/2025 || 11/21/2025
|-
| [https://cpate.ch/232 232] || [[ATL232|2025 CPAPA Tech Innovation Awards (Part 1/2)]] || [https://cpate.ch/atl232pub atl232pub] || 10/3/2025 || 11/14/2025
|-
| [https://cpate.ch/231 231] || [[ATL231|Interview with Mary Delaney, CEO, Karbon on AI (Part 2/2)]] || [https://cpate.ch/atl231pub atl231pub] || 10/3/2025 || 11/7/2025
|-
| [https://cpate.ch/230 230] || [[ATL230|Interview with Mary Delaney, CEO, Karbon (Part 1/2)]] || [https://cpate.ch/atl230pub atl230pub] || 10/3/2025 || 10/31/2025
|-
| [https://cpate.ch/229 229] || [[ATL229|AuditSight]] || [https://cpate.ch/atl229pub atl229pub] || 10/3/2025 || 10/24/2025
|-
| [https://cpate.ch/228 228] || [[ATL228|2025 AICPA Blockchain Symposium]] || [https://cpate.ch/atl228pub atl228pub] || 9/12/2025 || 10/17/2025
|-
| [https://cpate.ch/227 227] || [[ATL227|What is Advisory?]] || [https://cpate.ch/atl227pub atl227pub] || 10/3/2025 || 10/10/2025
|-
| [https://cpate.ch/226 226] || [[ATL226|Audit Automation Solutions]] || [https://cpate.ch/atl226pub atl226pub] || 9/12/2025 || 10/3/2025
|-
| [https://cpate.ch/225 225] || [[ATL225|Zoho - SMX and Balance]] || [https://cpate.ch/atl225pub atl225pub] || 9/12/2025 || 9/26/2025
|-
| [https://cpate.ch/224 224] || [[ATL224|Agentic AI Developments, Summer 2025]] || [https://cpate.ch/atl224pub atl224pub] || 8/7/2025 || 9/19/2025
|-
| [https://cpate.ch/223 223] || [[ATL223|BlueJ]] || [https://cpate.ch/atl223pub atl223pub] || 8/7/2025 || 9/12/2025
|-
| [https://cpate.ch/222 222] || [[ATL222|Ricoh ScanSnap iX2500]] || [https://cpate.ch/atl222pub atl222pub] || 8/7/2025 || 9/5/2025
|-
| [https://cpate.ch/221 221] || [[ATL221|AI Regulation Update]] || [https://cpate.ch/atl221pub atl221pub] || 8/7/2025 || 8/30/2025
|-
| [https://cpate.ch/220 220] || [[ATL220|Small Business Accounting Innovations 1H 2025]] || [https://cpate.ch/atl220pub atl220pub] || 7/11/2025 || 8/22/2025
|-
| [https://cpate.ch/219 219] || [[ATL219|AI Tax Developments 1H 2025]] || [https://cpate.ch/atl219pub atl219pub] || 7/11/2025 || 8/15/2025
|-
| [https://cpate.ch/218 218] || [[ATL218|AI Auditing Innovations 1H 2025]] || [https://cpate.ch/atl218pub atl218pub] || 7/11/2025 || 8/8/2025
|-
| [https://cpate.ch/217 217] || [[ATL217|Talent Shortage]] || [https://cpate.ch/atl217pub atl217pub] || 6/24/2025 || 8/2/2025
|-
| [https://cpate.ch/216 216] || [[ATL216|Scaling New Heights 2025 - AI Observations]] || [https://cpate.ch/atl216pub atl216pub] || 6/24/2025 || 7/28/2025
|-
| [https://cpate.ch/215 215] || [[ATL215|Scaling New Heights Show Floor]] || [https://cpate.ch/atl215pub atl215pub] || 6/24/2025 || 7/21/2025
|-
| [https://cpate.ch/214 214] || [[ATL214|Scaling New Heights 2025 Overview]] || [https://cpate.ch/atl214pub atl214pub] || 6/24/2025 || 7/21/2025
|-
| [https://cpate.ch/213 213] || [[ATL213|Key OBBBA Tax Changes]] || [https://cpate.ch/atl213pub atl213pub] || 7/11/2025 || 7/14/2025
|-
| [https://cpate.ch/212 212] || [[ATL212|AICPA ENGAGE 2025 Show Floor]] || [https://cpate.ch/atl212pub atl212pub] || 6/24/2025 || 7/11/2025
|-
| [https://cpate.ch/211 211] || [[ATL211|Accounting Leaders Think Tank Symposium 2025]] || [https://cpate.ch/atl211pub atl211pub] || 6/24/2025 || 7/3/2025
|-
| [https://cpate.ch/210 210] || [[ATL210|Microsoft Bookings]] || [https://cpate.ch/atl210pub atl210pub] || 5/13/2025 || 6/27/2025
|-
| [https://cpate.ch/209 209] || [[ATL209|AICPA ENGAGE 2025]] || [https://cpate.ch/atl209pub atl209pub] || 6/24/2025 || 6/20/2025
|-
| [https://cpate.ch/208 208] || [[ATL208|Microsoft Forms]] || [https://cpate.ch/atl208pub atl208pub] || 5/13/2025 || 6/12/2025
|-
| [https://cpate.ch/207 207] || [[ATL207|Power Automate]] || [https://cpate.ch/atl207pub atl207pub] || 5/13/2025 || 6/5/2025
|-
| [https://cpate.ch/206 206] || [[ATL206|CPAPA Readers Choice Awards]] || [https://cpate.ch/atl206pub atl206pub] || 5/13/2025 || 5/30/2025
|-
| [https://cpate.ch/205 205] || [[ATL205|Excel 40th Anniversary]] || [https://cpate.ch/atl205pub atl205pub] || 4/8/2025 || 5/16/2025
|-
| [https://cpate.ch/204 204] || [[ATL204|AICPA/CPA.com Startup Accelerator 2025]] || [https://cpate.ch/atl204pub atl204pub] || 4/8/2025 || 5/9/2025
|-
| [https://cpate.ch/203 203] || [[ATL203|AICPA/CPA.com AI Symposium]] || [https://cpate.ch/atl203pub atl203pub] || 4/8/2025 || 5/2/2025
|-
| [https://cpate.ch/202 202] || [[ATL202|Elizabeth Beastrom - TR]] || [https://cpate.ch/atl202pub atl202pub] || 3/7/2025 || 4/25/2025
|-
| [https://cpate.ch/201 201] || [[ATL201|Microsoft 50th Anniversary]] || [https://cpate.ch/atl201pub atl201pub] || 4/8/2025 || 4/18/2025
|-
| [https://cpate.ch/200 200] || [[ATL200|Safesend]] || [https://cpate.ch/atl200pub atl200pub] || 3/7/2025 || 4/11/2025
|-
| [https://cpate.ch/199 199] || [[ATL199|Brian Weiner - Family Office Resource Group]] || [https://cpate.ch/atl199pub atl199pub] || 3/7/2025 || 4/4/2025
|-
| [https://cpate.ch/198 198] || [[ATL198|Family Office Fundamentals]] || [https://cpate.ch/atl198pub atl198pub] || 3/7/2025 || 3/28/2025
|-
| [https://cpate.ch/197 197] || [[ATL197|CryptoCurrency Reserve]] || [https://cpate.ch/atl197pub atl197pub] || 3/7/2025 || 3/21/2025
|-
| [https://cpate.ch/196 196] || [[ATL196|End User Tech 1Q 2025]] || [https://cpate.ch/atl196pub atl196pub] || 2/7/2025 || 3/14/2025
|-
| [https://cpate.ch/195 195] || [[ATL195|Zoho For Firms: Practice, Payroll, Books, and Invoice]] || [https://cpate.ch/atl195pub atl195pub] || 2/7/2025 || 3/7/2025
|-
| [https://cpate.ch/194 194] || [[ATL194|Zoho's Platform for Finance and Operations]] || [https://cpate.ch/atl194pub atl194pub] || 2/7/2025 || 2/28/2025
|-
| [https://cpate.ch/193 193] || [[ATL193|AI in Practice: Zoho One]] || [https://cpate.ch/atl193pub atl193pub] || 2/7/2025 || 2/21/2025
|-
| [https://cpate.ch/192 192] || [[ATL192|AI in Practice: Acumatica ERP]] || [https://cpate.ch/atl192pub atl192pub] || 2/7/2025 || 2/14/2025
|-
| [https://cpate.ch/191 191] || [[ATL191|Payroll Solutions]] || [https://cpate.ch/atl191pub atl191pub] || 1/10/2025 || 2/7/2025
|-
| [https://cpate.ch/190 190] || [[ATL190|CES 2025: Startups]] || [https://cpate.ch/atl190pub atl190pub] || 1/10/2025 || 1/31/2025
|-
| [https://cpate.ch/190 190] || [[ATL190|CES 2025: ShowStoppers/Pepcom]] || [https://cpate.ch/atl190pub atl190pub] || 1/10/2025 || 1/24/2025
|-
| [https://cpate.ch/189 189] || [[ATL189|CES 2025: Award Winners]] || [https://cpate.ch/atl189pub atl189pub] || 1/10/2025 || 1/17/2025
|-
| [https://cpate.ch/188 188] || [[ATL188|Intuit Enterprise Suite]] || [https://cpate.ch/atl188pub atl188pub] || 12/5/2024 || 1/10/2025
|-
| [https://cpate.ch/187 187] || [[ATL187|Apxium]] || [https://cpate.ch/atl187pub atl187pub] || 12/5/2024 || 1/3/2025
|}

== Historical Episodes (2021-2024, ep #1-186) ==
{| class="wikitable sortable mw-collapsible mw-collapsed"
|'''Ep#'''
|'''Topic'''
|'''Record'''
'''Date'''
|'''Publish'''
'''Date'''
|-
|186
|2025 Predictions
|12/5/2024
|12/27/2024
|-
|185
|Intuit QuickBooks Connect
|12/5/2024
|12/20/2024
|-
|184
|Thomson Reuters Synergy 2024
|12/5/2024
|12/13/2024
|-
|183
|CCH Connections
|12/5/2024
|12/6/2024
|-
|182
|blue J
|10/4/2024
|11/30/2024
|-
|181
|Hubsync
|10/4/2024
|11/23/2024
|-
|180
|Soraban (PBC Tax Product)
|10/4/2024
|11/16/2024
|-
|179
|Tax GPT
|10/4/2024
|11/9/2024
|-
|178
|Liscio
|10/4/2024
|11/2/2024
|-
|177
|Syft Analytics
|9/6/2024
|10/25/2024
|-
|176
|Time Credit
|9/6/2024
|10/18/2024
|-
|175
|AI Privacy Laws and Regulations
|9/6/2024
|10/11/2024
|-
|174
|Software licensing and privacy
|9/6/2024
|10/4/2024
|-
|173
|2024 Tax & Accounting Awards
|9/6/2024
|9/27/2024
|-
|172
|Supervizor
|8/7/2024
|9/20/2024
|-
|171
|Aider
|8/7/2024
|9/13/2024
|-
|170
|Thomson Reuters Edge CoCounsel
|8/7/2024
|9/5/2024
|-
|169
|Wolters Kluwer T&A AnswerConnect
|8/7/2024
|8/30/2024
|-
|168
|ChatGPT and Copilot Prompting
|7/3/2024
|8/17/2024
|-
|167
|CYMA and CYMA Payroll
|7/3/2024
|8/10/2024
|-
|166
|SuiteFiles
|7/3/2024
|8/3/2024
|-
|165
|Canopy
|7/3/2024
|7/26/2024
|-
|164
|BQE Core
|7/3/2024
|7/19/2024
|-
|163
|Knuula and QuickFee
|6/12/2024
|7/12/2024
|-
|162
|CPA Practice Advisor Mashup
|6/12/2024
|7/5/2024
|-
|161
|Quickbooks Price Increases
|6/12/2024
|6/28/2024
|-
|160
|Artificial IntelligenceCPA ENGAGE 2024
|6/12/2024
|6/21/2024
|-
|159
|Laurel
|5/10/2024
|6/14/2024
|-
|158
|Black Ore Tax Autopilot
|5/10/2024
|6/7/2024
|-
|157
|SayAnchor - Tal
|5/10/2024
|5/31/2024
|-
|156
|Artificial IntelligenceGENCY / LLM's Passing the CPA Exam
|5/10/2024
|5/24/2024
|-
|155
|MakersHub.ai
|4/5/2024
|5/17/2024
|-
|154
|Digilence
|4/5/2024
|5/10/2024
|-
|153
|Datamatics
|4/5/2024
|5/3/2024
|-
|152
|AssurancePrep
|4/5/2024
|4/26/2024
|-
|151
|Aiwyn
|4/5/2024
|4/19/2024
|-
|150
|Rahul Mahna, Outsourced IT, Eisner Advisory
|4/5/2024
|4/12/2024
|-
|149
|CPAccounts PayableA TLS 2024
|3/1/2024
|4/5/2024
|-
|148
|SOBusiness Intelligence Analytics
|3/1/2024
|3/29/2024
|-
|147
|FedNow
|3/1/2024
|3/22/2024
|-
|146
|What is the Future of Desktop Accounting?
|3/1/2024
|3/15/2024
|-
|145
|Microsoft 365 Plans and Options
|3/1/2024
|3/15/2024
|-
|144
|StanfordTax
|2/9/2024
|3/8/2024
|-
|143
|QuickBooks Desktop Discontinuance
|2/9/2024
|3/1/2024
|-
|142
|Zoho Analyst Day 2024
|2/9/2024
|2/23/2024
|-
|141
|Oracle NetSuite Influencer Event 2024
|2/9/2024
|2/15/2024
|-
|140
|Acumatica Summit 2024
|2/9/2024
|2/9/2024
|-
|139
|CES 2024: Personal Tech
|1/12/2024
|2/5/2024
|-
|138
|CES 2024: Innovation Awards
|1/12/2024
|1/26/2024
|-
|137
|[https://youtu.be/dwi3Z5NNLpU?si=YovB9hkWuLh33qV9 CES 2024: Best Tech for Accountants]
|1/12/2024
|1/19/2024
|-
|136
|Thomson Reuters Synergy 2023
|12/5/2023
|1/12/2024
|-
|135
|Zoho Practice
|12/5/2023
|1/5/2024
|-
|134
|Tech Predictions for 2024
|12/5/2023
|12/29/2023
|-
|133
|Intuit QuickBooks Connect
|12/5/2023
|12/20/2023
|-
|132
|CCH Connections Conference
|11/8/2023
|12/15/2023
|-
|131
|Beneficial Ownership Information Reporting
|11/8/2023
|12/8/2023
|-
|130
|TeamMate Document Linker
|10/10/2023
|12/1/2023
|-
|129
|RAMP
|10/10/2023
|11/22/2023
|-
|128
|Clockwork AI
|10/10/2023
|11/16/2023
|-
|127
|Smartvault and Docdown
|10/10/2023
|11/10/2023
|-
|126
|Discerning Valid Content on AI
|9/8/2023
|11/3/2023
|-
|125
|Should You Upgrade Your Firm?
|9/8/2023
|10/25/2023
|-
|124
|Quantum Tech in Accounting
|9/8/2023
|10/18/2023
|-
|123
|Practice Management Trends
|6/9/2023
|10/6/2023
|-
|122
|Discussion of Rapid Close Tools
|8/4/2023
|9/28/2023
|-
|121
|Keeping Up With Technology
|8/4/2023
|9/14/2023
|-
|120
|Audit Sight
|8/4/2023
|9/12/2023
|-
|119
|Security Risks in New World
|5/12/2023
|9/7/2023
|-
|118
|Microsoft CoPilot
|5/12/2023
|8/31/2023
|-
|117
|Bookkeep / Jason Richelson
|7/7/2023
|8/23/2023
|-
|116
|FTC Safeguards Rule/IRS 4557
|8/4/2023
|8/16/2023
|-
|115
|AFOT Survey
|8/4/2023
|8/11/2023
|-
|114
|Audit Technology/Jeff Gramlich
|7/7/2023
|8/4/2023
|-
|113
|Verizon Data Breach Report
|7/7/2023
|7/28/2023
|-
|112
|Scaling New Heights 2023 Recap
|7/7/2023
|7/18/2023
|-
|111
|Outsourcing for Tax & Accounting Firms
|5/12/2023
|7/12/2023
|-
|110
|Tech Governance
|6/9/2023
|7/6/2023
|-
|109
|Audit Tech Trends
|6/9/2023
|6/29/2023
|-
|108
|AICPA ENGAGE 2023
|6/9/2023
|6/21/2023
|-
|107
|Data Snipper
|5/12/2023
|6/13/2023
|-
|106
|Large Language Models
|4/7/2023
|6/8/2023
|-
|105
|AI Results: Truthiness/Hallucinations
|4/7/2023
|5/30/2023
|-
|104
|Dall-E, MS Designer (Brian Livingston Competitors)
|4/7/2023
|5/23/2023
|-
|103
|MS AI: Bing, MS365 CoPilot, MS Designer
|4/7/2023
|5/17/2023
|-
|102
|ChatGPT and Accounting Firms
|4/7/2023
|5/11/2023
|-
|101
|Data Wrangling
|3/3/2023
|4/25/2023
|-
|100
|Recap of 2023 TLS
|3/3/2023
|4/11/2023
|-
|99
|MS Power Query
|3/3/2023
|4/11/2023
|-
|98
|Zoho Data Prep
|3/3/2023
|4/7/2023
|-
|97
|FloQast
|2/3/2023
|3/30/2023
|-
|96
|Acumatica
|2/3/2023
|3/23/2023
|-
|95
|Valid8
|2/3/2023
|3/16/2023
|-
|94
|CES 2023: Evolving Tech
|1/16/2023
|3/9/2023
|-
|93
|CES 2023: Firm Tech (Four Episodes)
|1/16/2023
|3/9/2023
|-
|92
|CES 2023: Industrial Tech
|1/16/2023
|3/8/2023
|-
|91
|CES 2023: New Standards
|1/16/2023
|3/7/2023
|-
|90
|CES 2023: Meeting Tech
|1/16/2023
|3/5/2023
|-
|89
|FreshBooks
|2/22/2023
|3/1/2023
|-
|88
|Zapier
|10/7/2022
|2/22/2023
|-
|87
|Validis
|10/7/2022
|2/14/2023
|-
|86
|LEO Satellites
|12/2/2022
|2/9/2023
|-
|85
|Hubdoc
|12/2/2022
|2/2/2023
|-
|84
|FileThis
|12/2/2022
|1/25/2023
|-
|83
|Booxkeeping/Max Emma
|10/7/2022
|1/19/2023
|-
|82
|Bill
|10/7/2022
|1/12/2023
|-
|81
|Conferences 2022 (CCH/TR)
|12/2/2022
|1/6/2023
|-
|80
|CData
|11/4/2022
|12/7/2022
|-
|79
|Backup Strategies for SOHO
|11/4/2022
|12/1/2022
|-
|78
|Zoho Invoice
|11/4/2022
|11/23/2022
|-
|77
|SmartVault
|9/9/2022
|11/17/2022
|-
|76
|Knuula
|11/4/2022
|11/9/2022
|-
|75
|e-Courier
|9/9/2022
|11/3/2022
|-
|74
|Doc-IT by IRIS
|9/9/2022
|10/19/2022
|-
|73
|Dext
|9/9/2022
|10/19/2022
|-
|72
|PlanGuru
|8/5/2022
|10/5/2022
|-
|71
|WeIntegrate
|8/5/2022
|10/5/2022
|-
|70
|DoMore CRM
|7/15/2022
|9/26/2022
|-
|69
|Desktime
|7/15/2022
|9/21/2022
|-
|68
|Xenett Autoreview
|8/5/2022
|9/13/2022
|-
|67
|Tallyfor
|8/5/2022
|9/5/2022
|-
|66
|nettTracker
|8/5/2022
|8/25/2022
|-
|65
|QuickBooks Desktop
|7/15/2022
|8/24/2022
|-
|64
|Zenwork/Tax1099
|7/15/2022
|8/18/2022
|-
|63
|BacoTech/Once Accounting
|4/14/2022
|8/6/2022
|-
|62
|Gilded
|4/14/2022
|8/6/2022
|-
|61
|Fieldguide
|4/14/2022
|7/28/2022
|-
|60
|Auvenir
|7/15/2022
|7/22/2022
|-
|59
|Zoho Expense
|6/17/2022
|7/10/2022
|-
|58
|Uncat
|6/17/2022
|7/8/2022
|-
|57
|Rewind
|6/17/2022
|6/29/2022
|-
|56
|Audit Miner
|6/17/2022
|6/24/2022
|-
|55
|CPA Firm Tech 2022
|5/16/2022
|6/2/2022
|-
|54
|CPA Firm Software Tech 2022
|5/16/2022
|6/2/2022
|-
|53
|Calendly Meeting Scheduler
|5/16/2022
|5/26/2022
|-
|52
|BizEKG from 4Impact Data
|5/16/2022
|5/20/2022
|-
|51
|Liscio
|2/4/2022
|5/12/2022
|-
|50
|Avalara
|2/4/2022
|5/5/2022
|-
|49
|Inflo (Inflo Workpapers)
|2/4/2022
|4/28/2022
|-
|48
|Suralink
|2/4/2022
|4/22/2022
|-
|47
|Pascal Workflow
|3/11/2022
|4/12/2022
|-
|46
|Thought Leadership Part 2
|3/11/2022
|3/29/2022
|-
|45
|Thought Leadership Part 1
|3/11/2022
|3/29/2022
|-
|44
|LivePlan (Palo Alto)
|1/11/2022
|3/23/2022
|-
|43
|IRIS/AccountantsWorld Part 2
|1/11/2022
|3/11/2022
|-
|42
|IRIS/AccountantsWorld Part 1
|1/11/2022
|3/11/2022
|-
|41
|Computer Hardware/CES
|1/11/2022
|3/4/2022
|-
|40
|Thomson Reuters AdvanceFlow
|11/5/2021
|2/10/2022
|-
|39
|Dynamics 365 Business Central
|11/5/2021
|2/8/2022
|-
|38
|Caseware Working Papers
|11/5/2021
|2/8/2022
|-
|37
|Paychex
|8/20/2021
|2/4/2022
|-
|36
|Gusto
|8/20/2021
|1/26/2022
|-
|35
|Intuit Payroll
|8/20/2021
|1/18/2022
|-
|34
|OnPay
|8/20/2021
|1/13/2022
|-
|33
|Corpay One
|10/1/2021
|1/7/2022
|-
|32
|Lucion FileCenter
|6/21/2021
|12/5/2021
|-
|31
|Rippling Payroll
|8/20/2021
|12/5/2021
|-
|30
|AccountantsWorld Accounting Power
|5/28/2021
|12/2/2021
|-
|29
|Spire
|10/1/2021
|11/22/2021
|-
|28
|Automatic Data Processing (ADP)
|8/20/2021
|11/15/2021
|-
|27
|NetSuite
|10/1/2021
|11/11/2021
|-
|26
|AccountantsWorld Cloud Cabinet
|5/28/2021
|11/5/2021
|-
|25
|Simplex Financials/PATH
|10/1/2021
|10/29/2021
|-
|24
|AccountantsWorld Payroll Relief
|5/28/2021
|10/20/2021
|-
|23
|eFileCabinet
|5/28/2021
|10/15/2021
|-
|22
|IRIS STAR Practice Management
|6/21/2021
|10/1/2021
|-
|21
|Ledgible Tax Pro
|6/21/2021
|9/24/2021
|-
|20
|Drake Tax
|7/23/2021
|9/1/2021
|-
|19
|Corvee
|6/21/2021
|8/31/2021
|-
|18
|ProConnect Tax
|7/23/2021
|8/23/2021
|-
|17
|TPS
|4/2/2021
|8/6/2021
|-
|16
|Clarity Practice Management
|4/2/2021
|7/29/2021
|-
|15
|CCH Axcess Document
|5/1/2021
|7/22/2021
|-
|14
|ONVIO Firm Management/Documents
|5/1/2021
|7/16/2021
|-
|13
|AccountantsWorld Practice Relief
|1/0/1900
|7/7/2021
|-
|12
|OfficeTools
|4/2/2021
|6/30/2021
|-
|11
|Karbon
|4/2/2021
|6/23/2021
|-
|10
|Jirav
|3/12/2021
|6/17/2021
|-
|9
|Canopy Practice Management
|4/2/2021
|6/9/2021
|-
|8
|Aero Workflow
|4/2/2021
|6/3/2021
|-
|7
|Abrigo ProfitCents
|3/12/2021
|5/27/2021
|-
|6
|Spotlight Reporting
|2/23/2021
|5/17/2021
|-
|5
|Qvinci
|3/12/2021
|5/14/2021
|-
|4
|Fathom
|2/23/2021
|4/29/2021
|-
|3
|Sage Intacct
|2/12/2021
|4/23/2021
|-
|2
|Xero
|2/9/2021
|4/15/2021
|-
|1
|QuickBooks Online
|2/12/2021
|4/2/2021
|}

== Episodes Scheduled or Recorded Not Published ==
{| class="wikitable sortable mw-collapsible"
!Recording Date
!Topic
!Seq
!Expected
Publication
|-
|4/3/2026
|Usinig Generative AI Projects
|997
|Evergreen
|-
|7/2/2026
|Hardware Hullabaloo
|4
|8/14/2026
|}

== External Links ==
* [https://www.cpapracticeadvisor.com/series/accounting-technology-lab-podcast/ Official Podcast Page on CPA Practice Advisor]
* [https://www.cpapracticeadvisor.com/ CPA Practice Advisor Home]

== See Also ==
* [[Randy Johnston]]
* [[Brian F. Tankersley]]
* [[CPA Practice Advisor]]

== Categories ==
[[Category:Accounting podcasts]]
[[Category:Technology podcasts]]
[[Category:CPA Practice Advisor]]
[[Category:2020s podcasts]]

ATL273

2026-09-01T01:43:14Z

Bftcpa606:

[[File:Slide20.JPG|thumb]]

= ATL273 — Reinventing Your Practice with Advisory =
'''With Guest Nancy Sperry of Sage'''

* '''Program:''' Accounting Technology Lab
* '''Episode:''' ATL273
* '''Release date:''' September 4, 2026
* '''Hosts:''' Randy Johnston and Brian F. Tankersley, CPA.CITP, CGMA
* '''Guest:''' Nancy Sperry, Senior Vice President of U.S. Partner Sales, Sage
* '''Approximate runtime:''' 33 minutes
* '''Primary topic:''' Using trusted AI, agentic automation, and the Sage partner ecosystem to move accounting professionals from transaction processing toward higher-value advisory work.
== 200-Word Episode Summary ==
In ATL273, Randy Johnston and Brian Tankersley talk with Nancy Sperry, Senior Vice President of U.S. Partner Sales at Sage, about how AI can help accounting firms and finance professionals reinvent their practices around advisory services. Sperry argues that AI adoption in accounting depends on trust: systems must be explainable, auditable, secure, controllable, and subject to human approval. That “glass box” approach can reduce the time professionals spend validating transactions and manipulating data, freeing them to interpret results, advise clients, and look forward instead of backward.

The discussion explores Sage Copilot, finance and close agents, partner-built agents, and a future agent marketplace where solutions created for one client may be reused across the Sage ecosystem. The hosts and Sperry also examine how AI could accelerate micro-vertical specialization in industries such as construction and nonprofit organizations, while integrations and Model Context Protocol connections may reduce dependence on traditional middleware and point solutions.

The episode closes with Sage’s broader platform strategy, including Sage Intacct, Sage HCM, and acquired products, and with a clear message for firms: advisory growth will require both AI-enabled productivity and disciplined governance, security, accountability, and human oversight as firms redesign workflows and deepen trusted relationships with clients today.
== Key Takeaways ==

* '''Trust is the gating factor for accounting AI.''' Explainability, auditability, approval workflows, security, and accountability matter as much as model capability.
* '''Advisory becomes more practical when the mechanical work shrinks.''' Automation can move professionals away from manipulating data and toward interpreting what the numbers mean.
* '''Finance will not become autonomous overnight.''' Sperry notes that only a small portion of finance functions are autonomous today; confidence must be earned through reliable results and controls.
* '''Agents create a new partner opportunity.''' Sage partners may be able to build agents for specific client problems and then distribute reusable solutions through a broader marketplace.
* '''Industry specialization can get much deeper.''' AI and agent builders may allow firms to move beyond broad verticals such as construction into highly specialized micro-vertical workflows.
* '''MCP and cross-system agents can change the technology stack.''' Agents that work across systems such as CRM, payroll, and ERP could eliminate some traditional integration layers—but also introduce new security concerns.
* '''Advisory becomes forward-looking.''' The opportunity is to spend less time looking through the rearview mirror and more time helping clients see through the windshield.
* '''Human oversight remains essential.''' The accountant, CFO, or advisor remains responsible for consequential decisions even when AI performs more of the underlying work.
* '''Sage is broadening the platform''' around finance, HR, payroll, expenses, construction, forecasting, practice management, and other adjacent workflows.
* '''The strategic opportunity is bigger than efficiency.''' AI can change the relationship between the accounting professional and the client by making interpretation, specialization, and continuous advice economically feasible.
== Catchy Quotes and Video Locations ==
''Times are based on the supplied transcript and may shift slightly if the published video contains a different intro, edit, or advertising insert.''

* '''00:55 — Nancy Sperry:''' “AI is the most exciting and really going faster than either of those two kind of major changes.”
* '''04:34 — Nancy Sperry:''' “Anything that is explainable and that I can click through and see the result… gives a lot of confidence.”
* '''06:48 — Brian Tankersley:''' “When the math’s not mathing, it’s not good for anybody in accounting.”
* '''08:24 — Nancy Sperry:''' “I see it being a really big revolution in the relationship.”
* '''10:37 — Nancy Sperry:''' “Turn the headlights on and see into the future.”
* '''13:36 — Nancy Sperry:''' Partners can “solve real business problems that are really critically important to that client.”
* '''15:58 — Randy Johnston:''' Advisory is “looking out the windshield as opposed to looking in the rearview mirror.”
* '''20:44 — Nancy Sperry:''' “Partners are the intersection of that for us at Sage.”
* '''26:26 — Nancy Sperry:''' Sage’s “glass box approach” is designed to provide confidence, control, oversight, and accountability.
* '''31:39 — Nancy Sperry:''' AI creates an opportunity for partners “to just create amazing outcomes.”
== 20 Social Media Posts ==

* '''Accounting advisory gets a lot easier when accountants stop spending most of their time manipulating data.''' ATL273 explores how trusted AI could shift the profession toward interpretation, judgment, and forward-looking advice. #AccountingTechnology #Advisory #AIinAccounting What does trustworthy AI actually mean for an accountant?
* '''Explainable. Auditable. Approvable. Secure. Accountable.''' Nancy Sperry of Sage joins ATL273 to explain why those controls matter. #AIGovernance #Accounting #Sage
* “'''When the math’s not mathing, it’s not good for anybody in accounting.'''” Brian Tankersley sums up one of the profession’s biggest concerns about blindly trusting AI output. #AIinAccounting #CPA #AccountingTech AI should help accountants spend less time looking in the rearview mirror and more time '''looking through the windshield.''' That is the advisory opportunity explored in ATL273. #AdvisoryServices #FutureOfAccounting
* The best accounting AI may not be the model with the flashiest demo. For regulated financial workflows, '''auditability, security, controls, and human approval''' may matter more. #AIGovernance #RiskManagement
* What happens when an accounting technology partner builds an AI agent that solves a difficult problem for one client—and can then offer it to hundreds more? ATL273 explores the emerging '''agent marketplace''' opportunity. #AgenticAI #AccountingTechnology
* An AI agent does not have to solve every accounting problem. A highly specialized agent that solves '''one expensive recurring problem really well''' may be far more valuable. #Automation #CPA
* Construction is not one market. Nonprofits are not one market. AI may allow accounting firms and technology partners to specialize far beyond traditional verticals into '''micro-vertical workflows.''' #Advisory #VerticalMarkets
* The future accounting technology stack may contain fewer traditional middleware products. Agents and MCP connections increasingly allow systems to communicate and execute work across platforms. '''That creates opportunity—and new security risks.''' #MCP #Cybersecurity #AI
* Advisory is not simply another service line. AI could fundamentally change the client relationship by giving accountants more time to '''interpret what happened, explain why it matters, and recommend what comes next.''' #TrustedAdvisor #Accounting
* Nancy Sperry says partners are critical to Sage’s AI strategy because they sit where software meets the messy reality of the customer’s business. That may make partners some of the most important AI innovators in accounting. #Sage #PartnerEcosystem
* Imagine building an AI agent for one unusual client workflow, refining it until it works, and then turning that intellectual property into a reusable solution. That is a very different business model for accounting technology consultants. #AgenticAI #Innovation
* AI can compress the journey from '''question → analysis → decision.''' But faster decisions only create value when the underlying data, controls, and reasoning can be trusted. #FinanceTransformation #AIGovernance
* Sage calls its approach a '''“glass box.”''' Accountants can see how the system reached an outcome instead of being expected to trust an unexplained black-box answer. That distinction matters in regulated workflows. #ExplainableAI #Accounting
* If automation handles more transaction processing, reconciliations, extraction, and validation, the accountant’s scarce resource increasingly becomes '''judgment.''' ATL273 examines what that means for advisory practices. #FutureOfWork #CPA
* The interesting question is no longer simply, “Can AI automate this?” A better question is: '''“What higher-value work can our people do once it does?”''' #AdvisoryServices #Automation #Accounting
* ERP, payroll, CRM, HCM, expense management, forecasting, practice management—the finance stack keeps expanding. Agents may provide a new connective layer across all of it. ATL273 looks at where Sage believes this is heading. #ERP #AgenticAI
* Technology partners have spent decades customizing software for clients. Agent builders could turn that same problem-solving expertise into reusable digital workers—and potentially a new source of recurring revenue. #PartnerChannel #AI
* Trustworthy AI is not just a technical requirement. It is a '''business-model requirement''' for accountants whose rofessional relationships depend on clients trusting their numbers and recommendations. #TrustedAdvisor #ProfessionalJudgment
* AI will change accounting faster than cloud computing did, according to Nancy Sperry. The firms that benefit most may be the ones that pair aggressive experimentation with equally serious attention to '''security, governance, controls, and human oversight.''' #AccountingTechnology #AIinAccounting #Sage
== Products, Services, Companies, and Social Accounts ==
Product names are grouped under their parent company when a separate official product account is not appropriate. “Not verified” means an official account could not be confirmed confidently enough to publish without guessing.
{| class="wikitable"
!Entity
!Products/services mentioned
!X
!Facebook
!LinkedIn
!Instagram
|-
|'''Sage'''
|Sage Intacct; Sage Copilot; finance agent; close agent; agent builders; proposed agent marketplace; Sage HCM; Sage 300; Sage Labs; construction and nonprofit solutions; Compass; AutoEntry; Criterion HCM; Fairsail; Brightpearl; Fyle; ForceManager/Sage Sales Management; Corecon; Futrli; GoProposal
|@SageNAmerica / @sagegroupplc
|Sage
|Sage
|@sageofficial
|-
|'''Microsoft'''
|Microsoft Copilot; underlying enterprise AI/compliance capabilities discussed by Brian
|@Microsoft
|Microsoft
|microsoft
|@microsoft
|-
|'''OpenAI'''
|ChatGPT
|@OpenAI
|@OpenAI
|OpenAI
|@openai
|-
|'''Anthropic'''
|Claude
|@AnthropicAI
|Not verified
|anthropicresearch
|Not verified
|-
|'''Google'''
|Gemini
|@Google
|Google
|google
|@google
|-
|'''Salesforce'''
|Salesforce CRM; example of an MCP-connected business system
|@salesforce
|Salesforce
|salesforce
|@salesforce
|-
|'''ADP'''
|ADP Payroll; example of an MCP-connected business system
|@ADP
|ADP
|adp
|ADP
|-
|'''Wolters Kluwer'''
|Professional accounting/tax technology; cited as another provider emphasizing trustworthy AI
|@Wolters_Kluwer
|wolterskluwer
|wolters-kluwer
|Not verified
|-
|'''Thomson Reuters'''
|Professional accounting/tax technology; cited as another provider emphasizing trustworthy AI
|@thomsonreuters
|@thomsonreuters
|thomson-reuters
|@thomsonreuters
|-
|'''LPGA'''
|Sage customer/partner example discussed in connection with specialized financial workflows
|@LPGA
|LPGA
|lpga
|@lpga_tour
|-
|'''ACT Construction'''
|Construction customer example as named in the transcript
|Not verified
|Not verified
|Not verified
|Not verified
|-
|'''CPA Practice Advisor'''
|Publisher of Accounting Technology Lab
|@CPAPracAdvisor
|cpapracticeadvisor
|cpa-practice-advisor
|@cpapracticeadvisor
|-
|'''Model Context Protocol (MCP)'''
|Cross-system AI integration protocol discussed by Randy
|N/A
|N/A
|N/A
|N/A
|}

=== Suggested Hashtags ===
<nowiki>#</nowiki>AccountingTechnology #AccountingTechnologyLab #AIinAccounting #AdvisoryServices #TrustedAdvisor #AgenticAI #Sage #SageIntacct #AIGovernance #ExplainableAI #Accounting #CPA #FinanceTransformation #Automation #FutureOfAccounting #PartnerChannel #MCP #Cybersecurity #InternalControls #ProfessionalJudgment

=== Newsletter / Website Teaser ===
Can AI finally give accountants enough time to become the advisors clients keep asking for?

In ATL273, Randy Johnston and Brian Tankersley welcome Nancy Sperry, Senior Vice President of U.S. Partner Sales at Sage, for a discussion about trusted AI, agentic workflows, advisory services, and the changing role of accounting technology partners.

The conversation goes well beyond automation. Nancy explains Sage’s “glass box” approach to explainability, auditability, approval, security, and accountability; discusses partner-built AI agents and a future agent marketplace; and explores how AI could enable much deeper industry specialization.

The larger opportunity is straightforward: automate more of the mechanical work so accountants can spend more time interpreting information, looking forward, and helping clients make better decisions.

==== Suggested Promotional Graphic ====
Primary headline: Reinventing Your Practice with Advisory

Secondary line:Trusted AI, Agents, and the New Role of the Accounting Advisor

Guest identification: Nancy Sperry, Senior Vice President, U.S. Partner Sales — Sage

==== Suggested visual callouts: ====
TRUSTED AI • ADVISORY • AGENTS • MICRO-VERTICALS

Best quote overlay:

“Turn the headlights on and see into the future.” — Nancy Sperry

Alternative humorous quote for social graphics:

“When the math’s not mathing, it’s not good for anybody in accounting.” — Brian Tankersley

Visual direction:

Use Nancy prominently with Randy and Brian, with subtle imagery suggesting a transition from transactional accounting/data processing toward forward-looking analytics. A restrained Sage-inspired green accent would reinforce the guest/company connection without allowing vendor branding to overwhelm the ATL identity.

2026-07-13T20:54:25Z

Bftcpa606: Created page with " Here's a short bash script to update Portainer on Debian (assuming it's running in Docker, the most common setup): <code>#!/bin/bash # Update Portainer container set -e echo "Stopping Portainer container..." docker stop portainer echo "Removing old container..." docker rm portainer echo "Pulling latest Portainer image..." docker pull portainer/portainer-ce:latest echo "Starting Portainer container..." docker run -d \ --name portainer \ --resta..."

Here's a short bash script to update Portainer on Debian (assuming it's running in Docker, the most common setup):
<code>#!/bin/bash

# Update Portainer container
set -e

echo "Stopping Portainer container..."
docker stop portainer

echo "Removing old container..."
docker rm portainer

echo "Pulling latest Portainer image..."
docker pull portainer/portainer-ce:latest

echo "Starting Portainer container..."
docker run -d \
--name portainer \
--restart always \
-p 8000:8000 \
-p 9000:9000 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v portainer_data:/data \
portainer/portainer-ce:latest

echo "Portainer updated successfully!"
docker ps | grep portainer</code>
'''Or if you prefer a simpler approach using <code>docker compose</code>:'''
<code>#!/bin/bash

cd /path/to/docker-compose/directory
docker compose pull portainer
docker compose up -d portainer

echo "Portainer updated!"</code>
'''If Portainer is installed standalone (less common):'''
<code>#!/bin/bash

PORTAINER_PATH="/opt/portainer"

systemctl stop portainer
cd $PORTAINER_PATH
wget <nowiki>https://github.com/portainer/portainer/releases/latest/download/portainer</nowiki>
chmod +x portainer
systemctl start portainer

echo "Portainer updated!"</code>
'''Which one do you use?''' I can refine the script based on your setup. Also, let me know if you need:

* Automatic cleanup of old images
* Backup before update
* Health check validation

Proxmox containers

2026-07-13T20:48:30Z

Bftcpa606: Created page with " = Running Containers on Proxmox VE = == A Procedural Tutorial for Administrators == == 1. Purpose == This tutorial explains the key concepts and procedures involved in running Linux containers on Proxmox Virtual Environment. After completing the tutorial, you should be able to: 1. Explain the difference between a container and a virtual machine. 2. Download a container operating-system template. 3. Create and configure an LXC co..."

= Running Containers on Proxmox VE =

== A Procedural Tutorial for Administrators ==

== 1. Purpose ==
This tutorial explains the key concepts and procedures involved in running Linux containers on Proxmox Virtual Environment.

After completing the tutorial, you should be able to:

1. Explain the difference between a container and a virtual machine.

2. Download a container operating-system template.

3. Create and configure an LXC container.

4. Allocate CPU, memory, storage, and networking resources.

5. Start, stop, update, and troubleshoot a container.

6. Configure backups, snapshots, and firewall protection.

7. Decide whether an application should run in an LXC container, a virtual machine, or Docker.

== 2. Understand Proxmox Container Architecture ==
Proxmox VE supports two primary forms of virtualization:

• '''KVM virtual machines'''

• '''LXC containers'''

A KVM virtual machine emulates a complete computer and runs its own kernel. An LXC container shares the Proxmox host’s Linux kernel but maintains a separate user space, filesystem, processes, network configuration, and resource limits.

Proxmox containers are designed primarily as '''system containers'''. A system container behaves like a small Linux server. It can run services such as:

• Web servers

• Database servers

• DNS servers

• File-sharing services

• Monitoring systems

• Internal business applications

• Reverse proxies

• Development environments

The Proxmox Container Toolkit, accessed through the pct command, manages LXC containers and integrates them with Proxmox storage, networking, clustering, firewall, backup, and high-availability features.

=== Container versus virtual machine ===
{| class="wikitable"
| valign="top" |Consideration
| valign="top" |LXC container
| valign="top" |KVM virtual machine
|-
| valign="top" |Kernel
| valign="top" |Shares the Proxmox host kernel
| valign="top" |Uses its own kernel
|-
| valign="top" |Operating systems
| valign="top" |Linux only
| valign="top" |Linux, Windows, BSD, and others
|-
| valign="top" |Startup time
| valign="top" |Usually a few seconds
| valign="top" |Usually longer
|-
| valign="top" |Resource overhead
| valign="top" |Low
| valign="top" |Higher
|-
| valign="top" |Isolation
| valign="top" |Good, but less complete than a VM
| valign="top" |Stronger isolation
|-
| valign="top" |Kernel modules
| valign="top" |Controlled by the host
| valign="top" |Managed inside the VM
|-
| valign="top" |Hardware passthrough
| valign="top" |More complicated
| valign="top" |Generally more flexible
|-
| valign="top" |Best use
| valign="top" |Lightweight Linux services
| valign="top" |Strong isolation or non-Linux workloads
|}
Use a container when the workload is Linux-based, does not require its own kernel, and benefits from low overhead.

Use a virtual machine when the workload:

• Runs Windows or another non-Linux operating system.

• Requires a custom kernel.

• Requires stronger security isolation.

• Requires complicated hardware passthrough.

• Runs software that is not compatible with LXC restrictions.

• Will host untrusted users or untrusted code.

== 3. Understand System Containers and Application Containers ==
An LXC container in Proxmox normally represents an entire Linux operating-system environment. For example, one container might run Debian with Nginx, PHP, SSH, systemd, and scheduled tasks.

This differs from the common Docker model, in which each container usually runs a single application or service.

A useful way to distinguish them is:

• '''Proxmox LXC:''' a lightweight Linux server.

• '''Docker container:''' a packaged application process.

Current Proxmox documentation also describes support for creating LXC-based containers from Open Container Initiative images. However, application-container support is identified as a technology preview. For ordinary production administration, conventional Linux LXC templates remain the more established approach.

== 4. Prepare the Proxmox Host ==
Before creating a container, confirm that the Proxmox node has:

• Available memory

• Available CPU capacity

• Suitable storage

• A working Linux bridge

• Current system updates

• A configured backup destination

=== Step 1: Check the Proxmox version ===
Open the Proxmox shell and run:

bash

pveversion -v

=== Step 2: Install available updates ===
Use the Proxmox web interface:

1. Select the Proxmox node.

2. Select '''Updates'''.

3. Click '''Refresh'''.

4. Review the available packages.

5. Click '''Upgrade'''.

Alternatively, use the host shell:

bash

apt update

apt full-upgrade

Reboot the host when a kernel or other major system component has been updated:

bash

reboot

Do not install ordinary application workloads directly on the Proxmox host. Keep the host dedicated to virtualization, storage, networking, backup, and cluster management.

=== Step 3: Review available storage ===
In the web interface:

1. Select '''Datacenter'''.

2. Select '''Storage'''.

3. Review each storage target.

4. Confirm that at least one storage target permits '''Container''' content.

5. Confirm that storage is available for '''Container templates''' and '''Backup files'''.

Typical storage roles might be:
{| class="wikitable"
| valign="top" |Storage name
| valign="top" |Typical contents
|-
| valign="top" |local
| valign="top" |Templates, ISO images, backup files
|-
| valign="top" |local-lvm
| valign="top" |Container and VM disks
|-
| valign="top" |local-zfs
| valign="top" |Container and VM datasets
|-
| valign="top" |pbs
| valign="top" |Proxmox Backup Server backups
|-
| valign="top" |nfs-backup
| valign="top" |Backup files on network storage
|}

=== Step 4: Review the network bridge ===
In the web interface:

1. Select the Proxmox node.

2. Select '''System'''.

3. Select '''Network'''.

4. Identify the primary bridge, commonly named vmbr0.

5. Confirm that the bridge is connected to the correct physical network interface.

A container’s virtual network adapter normally connects to a Linux bridge. The bridge acts like a virtual Ethernet switch that connects the container to the physical network.

== 5. Download a Container Template ==
A container template is a compressed Linux filesystem used to create new containers.

=== Using the web interface ===
1. Select the storage that accepts container templates, commonly '''local'''.

2. Select '''CT Templates'''.

3. Click '''Templates'''.

4. Select a Linux distribution.

5. Click '''Download'''.

6. Wait for the download task to finish.

Common choices include Debian, Ubuntu, AlmaLinux, Rocky Linux, Fedora, and Alpine Linux.

=== Using the command line ===
bash

pveam available

pveam available | grep debian

pveam update

pveam download local debian-13-standard_13.1-1_amd64.tar.zst

pveam list local

The exact filename changes as templates are updated. Use the filename shown by pveam available.

== 6. Plan the Container ==
Before clicking '''Create CT''', record the planned configuration.
{| class="wikitable"
| valign="top" |Setting
| valign="top" |Example
|-
| valign="top" |Container ID
| valign="top" |110
|-
| valign="top" |Hostname
| valign="top" |web01
|-
| valign="top" |Operating system
| valign="top" |Debian
|-
| valign="top" |Privilege mode
| valign="top" |Unprivileged
|-
| valign="top" |CPU cores
| valign="top" |2
|-
| valign="top" |Memory
| valign="top" |2 GB
|-
| valign="top" |Swap
| valign="top" |512 MB
|-
| valign="top" |Root disk
| valign="top" |16 GB
|-
| valign="top" |Bridge
| valign="top" |vmbr0
|-
| valign="top" |IPv4 address
| valign="top" |192.168.10.110/24
|-
| valign="top" |Gateway
| valign="top" |192.168.10.1
|-
| valign="top" |DNS domain
| valign="top" |example.local
|-
| valign="top" |DNS server
| valign="top" |192.168.10.5
|-
| valign="top" |Start at boot
| valign="top" |Yes
|-
| valign="top" |Firewall
| valign="top" |Yes
|-
| valign="top" |Backup
| valign="top" |Nightly
|}
Choose a descriptive hostname. Avoid generic names such as server1 when a functional name such as proxy01, wiki01, or monitor01 would be clearer.

== 7. Choose Between Privileged and Unprivileged Containers ==

=== Unprivileged container ===
In an unprivileged container, root inside the container is mapped to a non-root user ID on the Proxmox host.

Advantages include better protection against container escape and reduced impact of many container-level security problems.

Disadvantages include more complicated permissions for bind mounts, device access, and some nested workloads.

=== Privileged container ===
In a privileged container, root inside the container corresponds more directly to root privileges on the host.

This can simplify device access, certain network appliances, filesystem mounts, and legacy applications, but it offers weaker isolation.

=== Recommended rule ===
Use an '''unprivileged container by default'''. Create a privileged container only when the workload has a documented technical requirement that cannot reasonably be met with an unprivileged container.

== 8. Create a Container Through the Web Interface ==

=== Step 1: Open the creation wizard ===
1. Log in to the Proxmox web interface.

2. Select the desired node.

3. Click '''Create CT'''.

=== Step 2: Complete the General page ===
Enter the node, CT ID, hostname, optional resource pool, root password, and SSH public key. Enable '''Unprivileged container''' unless there is a documented reason not to.

=== Step 3: Select the template ===
Choose the template storage and downloaded operating-system template.

=== Step 4: Configure the root disk ===
Choose the storage target and disk size.
{| class="wikitable"
| valign="top" |Workload
| valign="top" |Starting root disk
|-
| valign="top" |DNS or small utility
| valign="top" |4–8 GB
|-
| valign="top" |Reverse proxy
| valign="top" |8–16 GB
|-
| valign="top" |General Linux server
| valign="top" |16–32 GB
|-
| valign="top" |Database server
| valign="top" |32 GB or more
|-
| valign="top" |File or media service
| valign="top" |Separate data mount recommended
|}

=== Step 5: Allocate CPU resources ===
Set cores, CPU limit if needed, and CPU units. Start small and increase resources based on measured demand.

=== Step 6: Allocate memory ===
Set memory and swap.
{| class="wikitable"
| valign="top" |Workload
| valign="top" |Memory
|-
| valign="top" |Small DNS or proxy server
| valign="top" |512 MB–1 GB
|-
| valign="top" |General web application
| valign="top" |1–4 GB
|-
| valign="top" |Database server
| valign="top" |Based on workload
|-
| valign="top" |Monitoring platform
| valign="top" |2–8 GB or more
|}
Leave sufficient memory for the Proxmox host, ZFS ARC if applicable, other guests, and backup operations.

=== Step 7: Configure networking ===
Enter the interface name, bridge, VLAN tag if needed, IP configuration, gateway, firewall setting, and optional rate limit.

For DHCP:

text

IPv4: DHCP

For a static address:

text

IPv4/CIDR: 192.168.10.110/24

Gateway: 192.168.10.1

=== Step 8: Configure DNS ===
Specify the DNS search domain and DNS server addresses.

=== Step 9: Confirm the configuration ===
Review the settings, optionally enable '''Start after created''', and click '''Finish'''.

== 9. Create a Container from the Command Line ==
bash

pct create 110 \

local:vztmpl/debian-13-standard_13.1-1_amd64.tar.zst \

--hostname web01 \

--unprivileged 1 \

--cores 2 \

--memory 2048 \

--swap 512 \

--rootfs local-lvm:16 \

--net0 name=eth0,bridge=vmbr0,ip=192.168.10.110/24,gw=192.168.10.1,firewall=1 \

--nameserver 192.168.10.5 \

--searchdomain example.local \

--ssh-public-keys /root/.ssh/id_ed25519.pub \

--onboot 1

Display the container configuration:

bash

pct config 110

== 10. Start and Access the Container ==
bash

pct start 110

pct status 110

pct console 110

pct enter 110

pct list

Use exit to leave the container shell.

== 11. Perform the Initial Operating-System Configuration ==
For Debian or Ubuntu:

bash

apt update

apt full-upgrade -y

Set the timezone:

bash

timedatectl set-timezone America/Chicago

Create an administrative user:

bash

adduser administrator

usermod -aG sudo administrator

Install and enable SSH if required:

bash

apt install openssh-server

systemctl enable --now ssh

Recommended SSH settings after key-based access has been tested:

text

PermitRootLogin no

PasswordAuthentication no

PubkeyAuthentication yes

Restart SSH:

bash

systemctl restart ssh

Install basic tools as needed:

bash

apt install curl wget vim-nox nano htop ca-certificates gnupg unzip

== 12. Manage Container Resources ==
bash

pct set 110 --memory 4096

pct set 110 --swap 1024

pct set 110 --cores 4

pct set 110 --onboot 1

pct set 110 --startup order=20,up=30,down=60

Startup ordering is useful when one service depends on another.

== 13. Add Storage to a Container ==

=== Proxmox-managed mount point ===
bash

pct set 110 --mp0 local-lvm:50,mp=/srv/data,backup=1

=== Bind mount ===
bash

mkdir -p /srv/shared

pct set 110 --mp0 /srv/shared,mp=/mnt/shared

Bind mounts require careful planning for user-ID mappings, backups, and migration.

== 14. Understand User-ID Mapping ==
A common default mapping is conceptually similar to:
{| class="wikitable"
| valign="top" |Container ID
| valign="top" |Host ID
|-
| valign="top" |0
| valign="top" |100000
|-
| valign="top" |1
| valign="top" |100001
|-
| valign="top" |1000
| valign="top" |101000
|}
For example:

bash

chown 101000:101000 /srv/shared

cat /etc/subuid

cat /etc/subgid

Verify mappings before changing ownership.

== 15. Configure Networking After Creation ==
bash

pct config 110

pct set 110 --net0 name=eth0,bridge=vmbr0,ip=dhcp,firewall=1

pct set 110 --net0 name=eth0,bridge=vmbr0,ip=192.168.10.110/24,gw=192.168.10.1,firewall=1

pct set 110 --net0 name=eth0,bridge=vmbr0,tag=20,ip=192.168.20.110/24,gw=192.168.20.1,firewall=1

== 16. Configure the Proxmox Firewall ==
Enable and review the firewall at the Datacenter, node, container, and interface levels as appropriate.

Example policy:
{| class="wikitable"
| valign="top" |Direction
| valign="top" |Action
| valign="top" |Protocol/port
| valign="top" |Source
|-
| valign="top" |In
| valign="top" |Accept
| valign="top" |TCP 22
| valign="top" |Administration subnet
|-
| valign="top" |In
| valign="top" |Accept
| valign="top" |TCP 443
| valign="top" |Internal networks
|-
| valign="top" |In
| valign="top" |Drop
| valign="top" |All others
| valign="top" |Any
|-
| valign="top" |Out
| valign="top" |Accept
| valign="top" |Required traffic
| valign="top" |Any
|}
Always create and test management-access rules before applying a default-deny policy.

== 17. Back Up Containers ==
Create a manual backup:

bash

vzdump 110 --storage nfs-backup --mode snapshot --compress zstd

Backup modes include snapshot, suspend, and stop.

A basic retention plan might include seven daily backups, four weekly backups, and several monthly backups.

Periodically test restores by restoring under a temporary ID, attaching the container to an isolated network, starting it, and verifying the operating system, application, and data.

== 18. Use Snapshots Carefully ==
bash

pct snapshot 110 before-upgrade

pct listsnapshot 110

pct rollback 110 before-upgrade

pct delsnapshot 110 before-upgrade

Snapshots are short-term rollback tools, not backups.

== 19. Clone and Template Containers ==
Before cloning, remove or regenerate machine-specific information such as hostnames, IP addresses, SSH host keys, application node identifiers, monitoring IDs, and database replication identities.

Use full clones when the new container should be independent.

== 20. Monitor Container Performance ==
Useful commands include:

bash

top

htop

free -h

df -h

ip address

ss -tulpn

journalctl -p warning

Investigate CPU, memory, storage, networking, application, and host contention issues before simply adding resources.

== 21. Stop, Reboot, and Shut Down Containers Correctly ==
bash

pct shutdown 110

pct reboot 110

pct stop 110

pct status 110

Use pct stop only when graceful shutdown fails or immediate termination is necessary.

== 22. Troubleshoot a Container That Will Not Start ==
bash

pct start 110 --debug

pct config 110

pvesm status

journalctl -xe

journalctl -xe | grep 110

df -h

zpool status

zfs list

pvs

vgs

lvs

The container configuration is normally stored under:

text

/etc/pve/lxc/110.conf

== 23. Troubleshoot Network Connectivity ==
From the host:

bash

ping 192.168.10.110

pct config 110

Inside the container:

bash

ip address

ip route

cat /etc/resolv.conf

ping 192.168.10.1

ping 1.1.1.1

getent hosts example.com

curl -I <nowiki>https://example.com</nowiki>

Check the interface, IP address, gateway, external routing, DNS, VLAN, bridge, and firewall rules in that order.

== 24. Use Nesting Only When Required ==
bash

pct set 110 --features nesting=1

Nesting may be required for Docker, Podman, some build systems, and certain sandboxing tools. It expands access to kernel-related interfaces and can reduce isolation.

== 25. Decide How to Run Docker ==

=== Option 1: Docker in a virtual machine ===
text

Proxmox host

└── Linux virtual machine

 └── Docker Engine

 ├── Application container

 ├── Database container

 └── Proxy container

This is usually the safest general recommendation for production Docker deployments.

=== Option 2: Docker in an LXC container ===
text

Proxmox host

└── LXC system container

 └── Docker Engine

 └── Application containers

This uses fewer resources but adds complexity around nesting, storage drivers, networking, AppArmor, cgroups, and device access.

=== Option 3: Docker directly on the Proxmox host ===
This is generally discouraged because Docker can alter firewall behavior, bridges, packet-filtering rules, storage configuration, and upgrade behavior.

== 26. Apply Container Security Practices ==
1. Prefer unprivileged containers.

2. Keep Proxmox VE updated.

3. Keep container operating systems updated.

4. Use SSH keys instead of passwords.

5. Disable unnecessary services.

6. Restrict management access by network.

7. Enable appropriate firewall rules.

8. Avoid exposing the Proxmox interface directly to the Internet.

9. Use multifactor authentication for administrators.

10. Back up container data.

11. Test restores.

12. Do not mount sensitive host directories into containers.

13. Avoid unnecessary nesting.

14. Avoid privileged containers unless technically required.

15. Use separate containers for unrelated services.

16. Monitor logs and resource usage.

17. Use a VM for untrusted code or workloads requiring stronger isolation.

== 27. Maintain Containers ==

=== Weekly tasks ===
• Review failed Proxmox tasks.

• Review backup results.

• Check storage utilization.

• Review high CPU or memory usage.

• Check container service health.

=== Monthly tasks ===
• Install operating-system updates.

• Review firewall rules.

• Review user accounts and SSH keys.

• Review available disk space.

• Verify monitoring and alerts.

• Test at least one representative backup restore.

=== Quarterly tasks ===
• Review resource allocations.

• Remove obsolete snapshots.

• Review privileged containers.

• Review containers with nesting enabled.

• Review unsupported or end-of-life operating systems.

• Confirm documentation and recovery procedures.

== 28. Example Deployment: Create a Small Web Server ==
Use these example settings:
{| class="wikitable"
| valign="top" |Setting
| valign="top" |Value
|-
| valign="top" |CT ID
| valign="top" |120
|-
| valign="top" |Hostname
| valign="top" |web01
|-
| valign="top" |Template
| valign="top" |Current Debian template
|-
| valign="top" |Unprivileged
| valign="top" |Yes
|-
| valign="top" |Cores
| valign="top" |2
|-
| valign="top" |Memory
| valign="top" |1 GB
|-
| valign="top" |Swap
| valign="top" |512 MB
|-
| valign="top" |Root disk
| valign="top" |8 GB
|-
| valign="top" |IP address
| valign="top" |192.168.10.120/24
|-
| valign="top" |Gateway
| valign="top" |192.168.10.1
|-
| valign="top" |Bridge
| valign="top" |vmbr0
|-
| valign="top" |Start at boot
| valign="top" |Yes
|-
| valign="top" |Firewall
| valign="top" |Yes
|}
Then run:

bash

pct start 120

pct enter 120

apt update

apt full-upgrade -y

apt install nginx -y

systemctl enable --now nginx

systemctl status nginx

ss -tulpn | grep :80

curl <nowiki>http://127.0.0.1</nowiki>

Test from another computer by opening:

text

<nowiki>http://192.168.10.120</nowiki>

Configure firewall access, add the container to the backup schedule, and document its purpose, owner, IP address, and recovery procedure.

== 29. Essential pct Command Reference ==
{| class="wikitable"
| valign="top" |Task
| valign="top" |Command
|-
| valign="top" |List containers
| valign="top" |pct list
|-
| valign="top" |Show status
| valign="top" |pct status 110
|-
| valign="top" |Show configuration
| valign="top" |pct config 110
|-
| valign="top" |Start
| valign="top" |pct start 110
|-
| valign="top" |Graceful shutdown
| valign="top" |pct shutdown 110
|-
| valign="top" |Stop immediately
| valign="top" |pct stop 110
|-
| valign="top" |Reboot
| valign="top" |pct reboot 110
|-
| valign="top" |Open console
| valign="top" |pct console 110
|-
| valign="top" |Enter shell
| valign="top" |pct enter 110
|-
| valign="top" |Set memory
| valign="top" |pct set 110 --memory 4096
|-
| valign="top" |Set CPU cores
| valign="top" |pct set 110 --cores 4
|-
| valign="top" |Enable startup
| valign="top" |pct set 110 --onboot 1
|-
| valign="top" |Create snapshot
| valign="top" |pct snapshot 110 snapshot-name
|-
| valign="top" |List snapshots
| valign="top" |pct listsnapshot 110
|-
| valign="top" |Roll back snapshot
| valign="top" |pct rollback 110 snapshot-name
|-
| valign="top" |Delete snapshot
| valign="top" |pct delsnapshot 110 snapshot-name
|-
| valign="top" |Create backup
| valign="top" |vzdump 110 --storage backup-storage
|-
| valign="top" |Display help
| valign="top" |pct help
|-
| valign="top" |Display command help
| valign="top" |pct help create
|}

== 30. Final Deployment Checklist ==
• [ ] The workload is appropriate for LXC.

• [ ] An unprivileged container was used unless privilege is required.

• [ ] CPU and memory limits are reasonable.

• [ ] The root disk has adequate free space.

• [ ] Application data is stored appropriately.

• [ ] The IP address and hostname are documented.

• [ ] DNS resolution works.

• [ ] The operating system is updated.

• [ ] SSH keys are configured.

• [ ] Unnecessary services are disabled.

• [ ] Firewall rules are enabled and tested.

• [ ] Automatic startup is configured.

• [ ] Startup order is configured when dependencies exist.

• [ ] Monitoring is active.

• [ ] Scheduled backups are active.

• [ ] A restore has been tested.

• [ ] Temporary snapshots have been removed.

• [ ] The application owner and recovery procedure are documented.

== Conclusion ==
Proxmox LXC containers provide an efficient way to run Linux server workloads with less overhead than complete virtual machines. Their efficiency comes from sharing the Proxmox host’s Linux kernel.

A well-managed deployment begins by selecting the correct virtualization model. Use an unprivileged LXC container for ordinary trusted Linux services, a KVM virtual machine for stronger isolation or specialized operating-system requirements, and a dedicated Linux VM for most production Docker environments.

Reliable container operations depend on more than creating the container. Administrators must also plan storage, networking, security, updates, monitoring, backups, and tested recovery procedures.

== Reference ==
Proxmox VE documentation: <nowiki>https://pve.proxmox.com/pve-docs/</nowiki>

Pentestgpt

2026-07-13T20:47:12Z

Bftcpa606: Created page with " = Setting Up PentestGPT in a Container on Proxmox — Beginner's Guide = ''Based on PentestGPT v1.0 (the December 2025 "agentic" release). Verified July 2026.'' == What you're actually building == PentestGPT changed a lot in v1.0. The old versions were a Python package you installed with pip. The current version ships as a '''Docker image''' that already contains Python 3.12, the pentest tools (nmap, netcat, whois, dnsutils, openvpn, etc.), and the Claude Code CLI it u..."

= Setting Up PentestGPT in a Container on Proxmox — Beginner's Guide =
''Based on PentestGPT v1.0 (the December 2025 "agentic" release). Verified July 2026.''

== What you're actually building ==
PentestGPT changed a lot in v1.0. The old versions were a Python package you installed with pip. The current version ships as a '''Docker image''' that already contains Python 3.12, the pentest tools (nmap, netcat, whois, dnsutils, openvpn, etc.), and the Claude Code CLI it uses for reasoning.

So on Proxmox you'll do three things:

1. Create a '''host''' on Proxmox (an LXC container or a VM) — this is your "container on Proxmox."

2. Install '''Docker''' inside that host.

3. Let PentestGPT's make commands build and run '''its own Docker container''' inside the host.

Yes — that's a container running a container. That's normal and expected here. The Proxmox LXC is the outer shell; PentestGPT lives in a Docker container inside it.

== Before you start ==
You'll need:

• '''A Proxmox VE host''' (version 8.x assumed) that you can reach via the web UI ''and'' open a shell on.

• '''An LLM provider credential.''' The autonomous agent uses Claude. You have four options, pick one:

– '''Anthropic API key''' — from console.anthropic.com. Pay-as-you-go. Simplest for a server. ''(Recommended for a headless box.)''

– '''Claude subscription (OAuth login)''' — requires a paid Claude Pro/Max subscription; you log in interactively.

– '''OpenRouter API key''' — from openrouter.ai, gives access to many models.

– '''Local LLM''' — point it at your own Ollama / LM Studio server (advanced).

• '''About 30–45 minutes''', most of which is the image build downloading.

'''A note on cost:''' because it calls a paid API, real runs cost money. The project's own published benchmarks average roughly '''$1.11 per successful task''' (median ~$0.42). Keep an eye on your API spend.

'''A note on scope:''' PentestGPT is a real offensive-security tool. Only point it at systems you own or have '''explicit written authorization''' to test — your own lab VMs, Hack The Box / TryHackMe targets, etc. The project ships with the same disclaimer.

== Decision: LXC container or VM? ==
Since you asked for a ''container'' on Proxmox, this guide leads with an '''LXC container'''. It's lighter and boots instantly.

One honest caveat: PentestGPT's Docker setup asks for the NET_ADMIN capability and a TUN device so it can dial VPNs (for Hack The Box / TryHackMe). Getting those working inside an LXC takes a couple of extra tweaks (privileged container + nesting + TUN passthrough), which this guide covers. If you '''don't''' need built-in VPN, you can skip the TUN step entirely.

If you'd rather avoid the LXC tweaks altogether, a small '''VM''' is the more bulletproof host — the TUN device and NET_ADMIN "just work" with no special config. There's a short VM section at the end; everything from Part 2 onward is identical.

== Part 1 — Create the LXC container ==

=== 1.1 Get a template (if you don't have one) ===
In the Proxmox web UI: click your storage (e.g. local) → '''CT Templates''' → '''Templates''', and download '''Ubuntu 24.04''' (recommended — it matches PentestGPT's base image) or Debian 13.

Or from the Proxmox host shell:

bash

pveam update

pveam available | grep -Ei 'ubuntu-24.04|debian-13'

pveam download local ubuntu-24.04-standard_24.04-2_amd64.tar.zst

''(The exact filename will vary — copy whatever the available command lists.)''

=== 1.2 Create the container ===
Click '''Create CT''' (top-right of the Proxmox UI) and set:
{| class="wikitable"
| valign="top" |Setting
| valign="top" |Value
| valign="top" |Why
|-
| valign="top" |'''Unprivileged container'''
| valign="top" |'''Unchecked''' (i.e. ''privileged'')
| valign="top" |Makes Docker-in-LXC far less painful for a beginner.
|-
| valign="top" |Hostname
| valign="top" |pentestgpt
| valign="top" |Anything you like.
|-
| valign="top" |Password / SSH key
| valign="top" |your choice
| valign="top" |You'll log in with this.
|-
| valign="top" |Template
| valign="top" |the one from 1.1
| valign="top" |—
|-
| valign="top" |Disk
| valign="top" |'''32 GB'''
| valign="top" |The image + tools need room.
|-
| valign="top" |CPU cores
| valign="top" |'''2–4'''
| valign="top" |More = faster reasoning.
|-
| valign="top" |Memory
| valign="top" |'''4096 MB min, 8192 MB better'''
| valign="top" |Compose defaults to an 8 GB limit.
|-
| valign="top" |Network
| valign="top" |DHCP or a static IP on your LAN
| valign="top" |Needs internet for the build + API.
|}
Click through and '''Finish''', but '''don't start it yet'''.

'''Why privileged?''' A privileged LXC is less isolated from the Proxmox host than an unprivileged one. For a homelab tool on a network you control, that's an acceptable trade for a smooth Docker experience. If you're security-conscious about the host itself, use the VM option instead.

=== 1.3 Enable nesting (required for Docker) ===
Select the new container in the UI → '''Options''' → '''Features''' → '''Edit''' → tick '''Nesting''' (and '''keyctl''' if shown) → '''OK'''.

=== 1.4 (Optional) Pass through the TUN device — only if you want built-in VPN ===
Skip this if you won't use Hack The Box / TryHackMe VPN from inside the tool.

On the '''Proxmox host shell''', edit the container's config (replace 100 with your CT's ID):

bash

nano /etc/pve/lxc/100.conf

Add these two lines at the bottom:

lxc.cgroup2.devices.allow: c 10:200 rwm

lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file

Save and exit.

=== 1.5 Start it and log in ===
Start the container ('''Start''' button), then open '''Console''', and log in as root with the password you set.

== Part 2 — Install Docker inside the container ==
Run these '''inside the LXC console''' (this is for Ubuntu/Debian):

bash

<nowiki>#</nowiki> Update the system

apt update && apt upgrade -y

<nowiki>#</nowiki> Tools we'll need

apt install -y ca-certificates curl gnupg git make

<nowiki>#</nowiki> Add Docker's official GPG key + repository

install -m 0755 -d /etc/apt/keyrings

curl -fsSL <nowiki>https://download.docker.com/linux/ubuntu/gpg</nowiki> -o /etc/apt/keyrings/docker.asc

chmod a+r /etc/apt/keyrings/docker.asc

echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] \

<nowiki>https://download.docker.com/linux/ubuntu</nowiki> $(. /etc/os-release && echo $VERSION_CODENAME) stable" \

| tee /etc/apt/sources.list.d/docker.list > /dev/null

<nowiki>#</nowiki> Install Docker Engine + Compose plugin

apt update

apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

<nowiki>#</nowiki> Confirm it works

docker run --rm hello-world

On '''Debian''' instead of Ubuntu, change the two ubuntu words in the repo URL to debian.

If hello-world prints a friendly message, Docker is working. If you get a permission or cgroup error, double-check that '''Nesting''' is enabled (Part 1.3) and reboot the container (reboot).

== Part 3 — Install PentestGPT ==
Still inside the LXC:

bash

<nowiki>#</nowiki> Clone with the benchmark suite included

git clone --recurse-submodules <nowiki>https://github.com/GreyDGL/PentestGPT.git</nowiki>

cd PentestGPT

<nowiki>#</nowiki> Build the Docker image (this is the slow step — grab a coffee)

make install

make install builds the pentestgpt:latest image from the included Dockerfile. First run pulls Ubuntu 24.04 and installs all the pentest tools, so it can take several minutes.

'''If you forgot --recurse-submodules:''' run git submodule update --init --recursive from inside the PentestGPT folder.

== Part 4 — Configure your LLM provider ==
bash

make config

This launches an interactive menu. Choose the option matching what you set up in "Before you start":

• '''Anthropic API''' → paste your sk-ant-... key. ''(Easiest for a server.)''

• '''Claude login (OAuth)''' → for subscription users; you'll finish the login in Part 5.

• '''OpenRouter''' → paste your OpenRouter key.

• '''Local LLM''' → point it at your Ollama/LM Studio server (see Troubleshooting for the host.docker.internal note).

Your credentials are stored in a persistent Docker volume, so you only do this once — they survive restarts.

== Part 5 — Connect and run your first test ==
bash

make connect

This starts the PentestGPT container (if it isn't already running) and drops you into a shell '''inside''' it, in the /workspace directory.

'''If you chose the Claude OAuth option''', log in once now:

bash

claude login

(Follow the URL/code prompt. This also persists across restarts.)

Now run the agent against a target:

bash

<nowiki>#</nowiki> Basic run against a target IP

pentestgpt --target 10.10.11.234

<nowiki>#</nowiki> Give it context to focus its approach

pentestgpt --target 10.10.11.50 --instruction "WordPress site, focus on plugin vulnerabilities"

<nowiki>#</nowiki> Cap how long it runs

pentestgpt --target 10.10.11.234 --max-iterations 5

This opens an interactive text UI where you watch the agent work through reconnaissance → vulnerability analysis → exploitation. Useful keys: '''F1''' = help, '''Ctrl+P''' = pause/resume, '''Ctrl+Q''' = quit.

When you're done, exit the shell and stop the container:

bash

make stop

Your image, config, and login all persist — next time it's just make connect.

== Managing the container day-to-day ==
Run these from the ~/PentestGPT folder inside your LXC:
{| class="wikitable"
| valign="top" |Command
| valign="top" |What it does
|-
| valign="top" |make connect
| valign="top" |Start + attach to the PentestGPT shell (your main entry point).
|-
| valign="top" |make stop
| valign="top" |Stop the container; all config/logins are kept.
|-
| valign="top" |make config
| valign="top" |Re-run provider setup (e.g. to switch keys).
|-
| valign="top" |make clean-docker
| valign="top" |Remove the container and image.
|-
| valign="top" |make docker-nuke
| valign="top" |Remove everything '''including saved logins''' (forces a fresh login next time).
|}
Monitor resource use anytime with:

bash

docker stats pentestgpt

== Optional: the multi-provider interactive mode ==
Inside the container, there's also a classic human-in-the-loop mode called pentestgpt-legacy. Unlike the autonomous agent (Claude-only), it talks to many providers — OpenAI, Anthropic, Gemini, DeepSeek, Grok, Qwen, Moonshot, and local Ollama — and you steer it with commands like next, more, todo, and discuss. Set the relevant API key(s) in a .env file first (copy .env.example), then:

bash

pentestgpt-legacy --list-models # see what's available/configured

pentestgpt-legacy # auto-pick best available models

== Turning off telemetry (optional) ==
PentestGPT sends anonymous usage metadata (session type, duration, which tools ran — '''not''' commands, credentials, or flag contents) to the project's analytics. To disable it:

bash

<nowiki>#</nowiki> per run

pentestgpt --target 10.10.11.234 --no-telemetry

<nowiki>#</nowiki> or globally, inside the container

export LANGFUSE_ENABLED=false

== If you'd rather use a VM instead of an LXC ==
A VM is the more foolproof host, especially if you want the VPN features. The only differences:

• In Proxmox, choose '''Create VM''' and install Ubuntu 24.04 Server (give it ~2–4 vCPU, 4–8 GB RAM, 32 GB disk).

• '''Skip Part 1.2's privileged setting, 1.3 nesting, and 1.4 TUN passthrough entirely''' — none of that is needed. /dev/net/tun and NET_ADMIN work natively.

• Everything from '''Part 2 (Install Docker)''' onward is exactly the same.

== Troubleshooting ==
'''docker: permission denied (as a non-root user):''' add your user to the docker group, then re-log: usermod -aG docker $USER and newgrp docker. (If you're running everything as root in the LXC, you won't hit this.)

'''make: command not found:''' you missed it in Part 2 — apt install -y make.

'''Docker won't start / cgroup errors in the LXC:''' confirm '''Nesting''' is enabled (Part 1.3), then reboot the container. If it persists, the privileged setting (Part 1.2) is the usual fix.

'''"Permission denied" writing to /workspace:''' the repo ships a helper — from the PentestGPT folder on the host, run ./fix-workspace-permissions.sh.

'''Local LLM can't connect (connection refused):''' from inside the Docker container, your host machine is reachable as host.docker.internal, '''not''' localhost. Point the model URL there (the compose file already maps it).

'''Image build fails downloading packages:''' check the container has working internet/DNS (ping github.com), and that your Proxmox network bridge is reachable.