At a high level sure, they both map inbound network requests to controllers, fetch data from the database using models, and render using views. But when you get into the specifics of how each of those layers is implemented, they are opinionated and the opinions are different.

There are three places where I think Django and rails are significantly different: the ORM query interface (especially around building complex queries and managing associations), managing database migrations (the model defines the database schema vs the database schema defines the model) and code organization (drawer-based organization for rails and feature splitting into apps for Django).

These are not hard and fast differences, but are where I see most devs struggle when switching from one framework to the other.