The following diagram highlights a very simplified view of a typical Riberry architecture. All interactions happens via a database backend.
It is important to note that at no point does the Riberry web application interact with the custom Celery workflows. Riberry itself is a backend system, so the web application is itself optional.
If the web application is unavailable, the custom Celery workflows are still functional as long as a connection with the configured database can be established.