How to separate superset-frontend and superset

[Lufffya]

I see that the superset-frontend and the supersetproject are in the same directory.
I hope it is a front-end and back-end separated project.
Can I deploy the superset-frontend separately on another machine and interact with the superset through REST API?

[rsaleev]

Any updates for Superset 6?

[rsaleev]

@dosu any info about separate frontend and backend service for version 6?

[dosubot[bot]]

There's no official plan or roadmap for separating the frontend and backend into independent services in Superset 6. The project continues to follow a monolithic deployment model where frontend and backend are deployed together [1].

That said, Superset 6 does include significant internal architectural refactoring — abstract DAO classes with dependency injection [2], a unified @api decorator for REST endpoints [3], and an extensions system using Module Federation [4] — but these improve modularity within the monolith rather than enabling separate service deployment.

A few relevant points:

• PR Fork #36816 attempted to create a standalone frontend bundle but was closed/rejected, suggesting this conflicts with the project's architectural direction.
• The SupersetClient in @superset-ui/core technically supports configuring a custom backend URL, but this isn't officially supported for production [1].
• JWT Bearer authentication in 6.0.1 has known issues where g.user isn't properly populated during API authorization, which would make a fully decoupled frontend difficult to operate [5].

In short: while the technical building blocks partially exist, there's no indication that official frontend/backend service separation is planned for version 6 or beyond.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.