Hi @LeeJBS ,
i agree with @OliverRodrigues that one of the primary focuses of portals was/is to expose dynamics data and that is still a good fit.
Nevertheless, Microsoft takes a new path with power app portals that you provision a so called cds environment, which is in no means a crm environment. You just have a backend for the website you run.
This backend is much more than a database. It is part of a large ecosystem and you can leverage all possibilities of power automate and backend integrations to many other services. And when it comes to designing entities (what is comparable to creating database tables) you have a very nice interface of doing so.
As you have to write the businesslogic also with another approach, you could still think about using portals as a website.
But when you find a service, where you already can setup that kind of ruling stuff, its definetely preferrable.
So, no advice but keep in mind: PowerAppPortals already brings a full infrastructure for running a website and the programmingstack will be javascript and liquid templating and may be some plugins/workflows/power automates to deal with your data.
Hope this does not confuse too much,
Christian
PS no, i am not employed at microsoft 🙂
PPS i work with portals since it was adx and i am coming from a programming background. Yes, our customers come from a crm background but when it comes to external integration of data, power app portals is not a bad choice for doing so. We also have customers, who use a mix of power apps and power app portals with the same cds environment (without crm). If you need that kind of scenarios, i would give cds driven stuff a try 🙂