What about self hosting?

Question

I have some questions. \u000a\u000a1) what do you mean by self hosting? i work on an app or website in your platform, then i can deply the production website on my hosting, or will i install no code on my server and work on that? \u000a\u000a2) if i work on your server then deploy on mine, what resource will i consume of my plan?\u000a\u000a3) for selfhosted what i should need as a machine? do i need some frameworks etc, or does nocode x do it itself? (for example if i have an ubuntu vps, do i need to prepare the machine installing things, or i just give nocode\u002Dx permission and it does anything alone?)\u000a\u000a4) docs is a little lacking about self hosting \u003B) \u000a\u000athanks

Wim_NoCode-X · Answer

Thank you for your questions! Let me clarify everything about self\u002Dhosting and how it works with NoCode\u002DX.\u000a\u000aWHAT DOES SELF\u002DHOSTING MEAN?\u000a\u000aSelf\u002Dhosting allows you to install and run the NoCode\u002DX platform on your own infrastructure. You can take a hybrid approach: develop your app or website on our SaaS platform and then deploy it to your private or public hosting environment. For example, you can work on the SaaS platform for development and testing, then deploy the production version on your self\u002Dhosted setup.\u000a\u000aIf you choose to self\u002Dhost entirely, you’ll install NoCode\u002DX on your server and work directly on that environment. This requires a dedicated self\u002Dhosted license, which is separate from the AppSumo SaaS license. You can find more details here: https://docs.nocode\u002Dx.com/when\u002Dto\u002Dchoose\u002Dnocode\u002Dx/Self%20hosted\u000a\u000aIf you have ideas about cost/value propositions for self\u002Dhosting, feel free to share them with us. We’re exploring licensing models based on resource consumption and business value, and your input is always welcome!\u000a\u000aWHAT RESOURCES WILL I CONSUME IF I WORK ON YOUR SERVER AND DEPLOY ON MINE?\u000a\u000aIf you develop on the SaaS platform (AppSumo license) and then deploy to your self\u002Dhosted environment, the resources consumed during development will count against your SaaS plan. However, once you deploy to your self\u002Dhosted environment, the SaaS resources will no longer be used.\u000a\u000aWHAT DO I NEED FOR SELF\u002DHOSTING?\u000a\u000aFor self\u002Dhosting, the preferred setup is a Kubernetes (K8s) environment. While Docker can also work, it requires more manual configuration. Here’s what you’ll need:\u000a\u000a* A Kubernetes runtime (or Docker if you prefer).\u000a* Sufficient storage, CPU, and memory for your application (https://docs.nocode\u002Dx.com/when\u002Dto\u002Dchoose\u002Dnocode\u002Dx/Self%20hosted).\u000a* Backup storage that is out\u002Dof\u002Dband. For example, if you’re hosting locally, consider using cloud\u002Dbased storage for backups to protect against disasters. This principle also applies to cloud\u002Dhosted solutions.\u000aIf you’re using an Ubuntu VPS, you don’t need to prepare the machine extensively. Once your Kubernetes services are ready, you can deploy NoCode\u002DX using a HELM chart. No system\u002Dlevel access is required, as everything is handled through Kubernetes. After deployment, you’ll be ready to go!\u000a\u000aDOCUMENTATION FOR SELF\u002DHOSTING\u000a\u000aYou’re absolutely right that the self\u002Dhosting documentation could use more detail. We’re actively working on improving the manual and guides to make integration as seamless as possible.\u000a\u000aGETTING STARTED\u000a\u000aTo help you get started, check out our YouTube channel for tutorials and tips:\u000aLINK: https://www.youtube.com/@nocode\u002Dx\u000a\u000aIf you have any further questions or need assistance with self\u002Dhosting, feel free to reach out. We’re here to help you succeed!

NoCode-X

Share NoCode-X

Related questions