Databasus and WAL-G have completely different architectures. WAL-G is installed on the server with DB. Databasus connects to the database remotely.
WAL-G is about PITR backups, Databasus is about logical ones.
From one side, Databasus usually is slower when database is large.
From another side, it's much easier to use (especially when you have a lot of DBs).
In the future, I am considering implementing incremental backups and following a similar approach as WAL-G or pgBackRest do. But it will be one of options, not mandatory one
WAL-G is about PITR backups, Databasus is about logical ones.
From one side, Databasus usually is slower when database is large.
From another side, it's much easier to use (especially when you have a lot of DBs).
In the future, I am considering implementing incremental backups and following a similar approach as WAL-G or pgBackRest do. But it will be one of options, not mandatory one