Self-Hosted Architecture
Self-hosted architecture is pretty simple; you have the pre-built app, served with Deno in one container, which then connects to Postgres in another container. The app includes some API endpoints which can be called to keep data updated, monitor domains and trigger notifications (via webhooks), so you might want a third container to manage crons to call these endpoints periodically.
How this differs from the managed instance?
This differs slightly from the managed instance, as self-hosted is designed to be standalone, and run in an easy docker-compose without being reliant upon external services.
Whereas the managed instance has dependencies on third-parties, which must be configured. You can switch the version at anytime, using the DL_ENV_TYPE environmental variable, which is set to selfHosted by default. (but note that you will need to configure the third-party platforms and services if you switch to managed). Either way, you can find the docs for all the services used here.
