Autonomous product teams are key for sustainable software delivery. But what does autonomy really mean? Do we expect the team to set up CI/CD, automate infra, test/UX all the things, and, of course, run and monitor their product? And still deliver features? Four fundamental team topologies and three interaction modes can help.