- July 2026 (3)
- June 2026 (7)
- May 2026 (2)
- April 2026 (11)
- March 2026 (3)
- February 2026 (4)
- January 2026 (4)
- December 2025 (1)
- November 2025 (3)
- October 2025 (9)
- September 2025 (3)
- August 2025 (5)
- July 2025 (1)
- June 2025 (2)
- May 2025 (3)
- April 2025 (2)
- March 2025 (7)
- February 2025 (10)
- January 2025 (6)
- December 2024 (7)
- September 2024 (1)
- August 2024 (2)
- July 2024 (2)
- May 2024 (2)
- April 2024 (2)
- February 2024 (2)
- April 2023 (1)
- March 2023 (2)
- September 2022 (1)
- February 2022 (1)
- November 2021 (1)
- March 2021 (1)
- February 2021 (2)
- August 2019 (1)
- November 2018 (1)
- May 2017 (1)
- December 2016 (1)
- April 2016 (1)
- August 2015 (1)
- December 2014 (1)
- August 2014 (1)
- March 2014 (1)
- December 2013 (1)
- October 2013 (3)
- September 2013 (4)
- August 2013 (2)
- July 2013 (1)
- June 2013 (1)
- February 2013 (1)
- October 2012 (1)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (1)
- October 2011 (1)
- June 2011 (1)
- May 2011 (1)
- April 2011 (1)
- March 2011 (1)
- February 2011 (1)
- January 2011 (1)
- December 2010 (3)
- November 2010 (1)
- October 2010 (1)
- September 2010 (1)
- August 2010 (1)
- July 2010 (1)
- May 2010 (3)
- April 2010 (1)
- March 2010 (2)
- February 2010 (3)
- January 2010 (4)
- December 2009 (2)
- November 2009 (5)
- October 2009 (2)
- September 2009 (2)
- August 2009 (3)
- July 2009 (1)
- May 2009 (1)
- April 2009 (1)
- March 2009 (5)
- February 2009 (5)
- January 2009 (5)
- December 2008 (3)
- November 2008 (7)
- October 2008 (4)
- September 2008 (2)
- August 2008 (1)
- July 2008 (1)
- June 2008 (1)
- May 2008 (1)
- April 2008 (1)
- January 2008 (4)
- December 2007 (3)
- March 2007 (3)
- February 2007 (1)
- January 2007 (2)
- December 2006 (4)
- November 2006 (18)
- AI (90)
- TIL deep dives (77)
- Python (72)
- LLM from scratch (48)
- Resolver One (34)
- PyTorch (21)
- TIL (21)
- Blogkeeping (18)
- PythonAnywhere (17)
- Linux (16)
- Startups (15)
- Gadgets (13)
- Hugging Face (13)
- NSLU2 offsite backup project (13)
- Funny (11)
- Musings (11)
- Finance (10)
- Fine-tuning LLMs (10)
- C (9)
- Personal (8)
- Robotics (8)
- Website design (8)
- JAX (7)
- 3D (5)
- Quick links (5)
- Rants (5)
- Cryptography (4)
- JavaScript (4)
- Music (4)
- Oddities (4)
- Talks (4)
- Dirigible (3)
- Eee (3)
- Memes (3)
- Politics (3)
- Django (2)
- GPU Computing (2)
- LaTeX (2)
- MathML (2)
- OLPC XO (2)
- Retro Language Models (2)
- Space (2)
- VoIP (2)
- Copyright (1)
- Golang (1)
- Microprojects (1)
- poppy the training box (1)
- Raspberry Pi (1)
- Software development tools (1)
- Agile Abstractions
- Astral Codex Ten
- :: (Bloggable a) => a -> IO ()
- David Friedman's Substack
- Econ & Energy
- Entrepreneurial Geekiness
- For some value of "Magic"
- Hackaday
- kaleidic.ai newsletter
- Knowing.NET
- Language Log
- Millennium Hand
- ntoll.org
- Obey the Testing Goat!
- PK
- PythonAnywhere News
- Simon Willison's Weblog
- Societive
- Software Deviser
- Some opinions, held with varying degrees of certainty
- tartley.com
Leaving PythonAnywhere
Today was my last day at PythonAnywhere, the platform I co-founded back in 2011. We sold the business to Anaconda in 2022, and I'm confident that it's in good hands -- in particular, Glenn, Filip and Piotr from the original team are all staying on, and with the help of Nina, Lee and Alex who joined after the acquisition, plus the support of the larger Anaconda organisation, there's a fantastic future ahead for the platform and the community we've built around it.
It's been quite the ride! Back in late 2005, Robert, Patrick and I founded a company called Resolver Systems. Our goal was to free the world from messy Excel spreadsheets, and we built an amazing team1 that created an amazing tool, called Resolver One -- a spreadsheet designed to integrate Python from the ground up. Unfortunately we made all of the textbook startup mistakes -- in particular, building in secret for more than a year and only getting it in front of potential users when that was done. Added to that, we had the bad luck of releasing a product targeting financial users in 2008, just in time for many of our potential customers to start going bust. Ooops.
We pushed ahead for a while, but eventually in 2010 we pivoted to Dirigible, a cloud-based version of Resolver One -- a Pythonic spreadsheet, but web-based. And we'd learned our lession: we got it from idea to first release in less than a month, and started building up a group of active users.
Within six months or so, we realised that our users were using Dirigible differently to how we imagined. They were ignoring the spreadsheet grid entirely and just using it as a Python cloud IDE. "It would be great if I could host a website through this thing", they told us. "Any chance of adding on a MySQL database so that I can store stuff there?"
We had a direction to take it -- one that people really seemed keen on! So in early 2011, it was time to pivot again, and Dirigible-with-the-spreadsheet-grid-removed became PythonAnywhere.
From there, things started taking off; I posted about the first ten years on the company blog with the details, but I remember the milestones: cocktails under Smithfield Market when we hit 1,000 customers; the day our revenue covered our AWS bill; the day it covered everything except salaries, then everyone’s salaries except mine -- and then, the day we broke even, independent and sustainable.
A few years after that, towards the end of 2021, a mutual friend put me in touch with Peter Wang at Anaconda. We talked about possibilities for working together; after a while, the idea of an acquisition came up, and it was obviously the right move. We had a popular and growing platform with technology that allowed us to host hundreds of thousands of users efficiently enough to offer free accounts; with Anaconda's leading position in the Python market -- especially in data science -- and its resources, not only could PythonAnywhere grow faster and better, but we could also help Anaconda build new products to cement its position. So, after some negotiations, in June 2022 we became part of the Anaconda family.
There were sad moments too, of course; of the original team, only Glenn and I remained (both from the Resolver days). Jonathan had moved on not long after we pivoted to PythonAnywhere, then Hansel after we'd been running for a few years, then Harry 2, and then Conrad.
Now, finally, it's time for me to move on too. It's hard to leave -- I feel like I've been finding excuses to delay it for months!
But fourteen years is a long time to work on something, and the pressure of running a startup, followed by the stress of due diligence and everything else that goes into an acquisition, has all built up. I stayed on at Anaconda as PythonAnywhere team lead for three years after the sale to help with the transition and make sure everything was in good shape. And -- as far as one can be in a changing world -- I'm confident that it is now.
It's been an amazing fourteen years, and I'd like to thank everyone who was involved -- the team, of course, but also the community around the platform. To everyone who's ever signed up, subscribed, filed a bug, made a suggestion, or told a friend -- to all of our paying customers, and everyone who's supported us in other ways -- thank you! PythonAnywhere exists thanks to you.
So, what next? My plan is to take a year off to clear my head, reset, and relax. Sara, my wife, is betting that I'll last less than six months before I get bored and start something else.
She may be right.
In the meantime, you can expect posting to continue here as normal -- maybe even more than in the past, what with all the extra time :-)
And finally -- if you have any PythonAnywhere stories to share, please do leave a comment below. I'd love to hear from you!
-
Including the inimitable Michael Foord, who was sadly taken from us before his time earlier this year. ↩
-
Not only an awesome developer, but also a gonzo marketer par excellence, and the author of what is either the best or the worst company newsletter ever written. ↩