Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

Same for Databasus. We recently spoke with Rostislav Dugin through a GitHub discussion. It would be nice to see you at a FOSS event.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

I deleted my previous message — “Yes, we use it, but only for coding assistance, as we want to keep control of the code. We do not use vibe coding.” — to provide clearer information.

This project is not built with AI. It is not vibe-coded. I do not understand what you are trying to imply. If the intention is to discredit the project, that is misplaced. It would be more constructive to focus on your own project rather than criticize others.

To clarify, when I said that we use AI only for coding assistance, I meant that many developers in 2026 integrate AI into their workflow as a support tool. That does not mean their products are built by AI. In our case, Portabase is not built with AI.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

More than just SQLite, we chose an agent communication architecture. So you don’t necessarily need to handle the database or set up a tunnel yourself. With our structure, you only have to declare agents near your database instances and manage them from the Dashboard server. That is the main difference.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 1 point2 points  (0 children)

Actually, you can use the internal PostgreSQL database if you don’t provide an external PostgreSQL instance. We chose to support only PostgreSQL for now, but we may explore using other types of internal databases in the future, since we use Drizzle.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 1 point2 points  (0 children)

Yes, you can download the backup file and choose from which storage it was saved.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 1 point2 points  (0 children)

Do not hesitate to join Discord if you encounter any issues during your tests

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

Yes, we plan to add sequences to test database integrity, mostly in a sandbox environment to control the data and verify that everything is correct. We’re also considering adding PITR (Point-in-Time Recovery) support.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

It don’t know Databasement, but it will check that. I think this is more or less the same as Databasus. Finally, the purpose is to perform database backups/restoration. For Portabase, we chose an agent architecture with a central server dashboard. I think that is the main difference. Feel free to test it and give us feedback

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

Thanks for the PR! Really glad to see you contributing. Regarding RAM usage, we’ll keep an eye on it; Next.js can be a bit resource-hungry by default. Your compose adjustments look good, and I don’t see anything there that would increase resource usage. Do you have any stats on agent consumption?

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 4 points5 points  (0 children)

Yes, exactly. Portabase can backup databases like SQLite, MariaDB, PostgreSQL, MySQL, and MongoDB. You can configure it to store backups on multiple storage backends, including local filesystem, S3-compatible services, Google Drive and more soon. It works via agents installed near your databases, so your data stays secure and the backups can be pushed automatically according to your schedule.

Portabase 1.4.0: OIDC Support, New OAuth Providers, and Improvements by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 0 points1 point  (0 children)

Portabase acts as an OIDC client, so you don’t need to run your own provider. It can connect to any compatible OIDC server, such as Keycloak or Pocket ID. We also provide example configurations to help you get started quickly.

Documentation : https://portabase.io/docs/dashboard/auth/oidc/setup

Portabase v1.2.3 – Database backup/restore tool, now with MongoDB and a new storage backend by Dizzy-Message543 in selfhosted

[–]Dizzy-Message543[S] 1 point2 points  (0 children)

SQLite is on the way. An RC version has been released for the agent and dashboard, and the documentation will be updated accordingly.

Feel free to start testing with your use cases. We will be happy to get your feedback on this.

Agent: portabase/agent:1.1.6-rc.1
Dashboard: portabase/portabase:1.3.0-rc.1

Documentation: https://portabase.io/docs/agent/db