I am evaluating Plasmic to determine if it meets our company’s needs, specifically regarding its self-hosted options.
Self-hosted means the generated code can be self hosted, not the codegen engine or plasmic UI editor. Is this correct? Therefore, every time a code need to be generate, the build script must request the plasmic-hosted platform to generate the code. In that case is not possible to build a project without a internet connection and a plasmic account.
Does this also means that it is not possible to integrate with a database inside a private network?
Plasmic can be self-hosted both ways. The generated code can absolutely be self-hosted, and that’s how most of our users use it. The codegen engine and editor can also be self-hosted; see our open-source repo for details.
Generally, if you have a database on a private network, you’d want to expose it via a publicly available and secured API server instead. Let me know if you have more specific requirements here.
Could you kindly point me to any specific guides on self-hosting the codegen engine and editor? I’ve searched extensively and haven’t found documentation on this.
It seems to me more advantageous to use Plasmic’s direct database integration rather than setting up a REST API to integrate. I assume that database integration would allow Plasmic to automatically introspect schemas and fields from the database, simplifying the process.
Since my database and Plasmic are both within the same private network, I would prefer to keep the direct connection private, with Plasmic handling the creation of necessary API endpoints.
I guess if I am able to self host plasmic studio this issue will be solved since plasmic studio would be within the same private network.