#HDS Applications

1 messages · Page 1 of 1 (latest)

rugged nimbus
#

Hi Emergent Team,

I am currently evaluating Emergent.sh for the development of a professional CRM dedicated to the healthcare industry. Due to legal requirements in France (HDS certification), the final application must be self-hosted on a specific HDS-certified infrastructure.

I have a few technical questions regarding the portability and architecture of the apps generated by your platform:

  1. Full Code Portability & Dockerization

Once the development is complete, does the GitHub export include a production-ready Dockerfile and docker-compose.yml?

After exporting the code, is the application 100% independent from Emergent.sh infrastructure, or are there any proprietary dependencies or "phone-home" logic remaining in the backend?

  1. External MongoDB Integration

Can I use an external, remote MongoDB instance (hosted on an HDS server in France) as the primary database during the development phase?

Does your platform support whitelisting specific IP addresses so my HDS host can allow incoming connections from your build

  1. Professional Services & Deployment Support

Do you offer professional services or paid consulting to assist with the final migration and deployment of the application onto a third-party infrastructure?

Specifically, if we encounter issues configuring the Docker environment or the production-grade security settings on our HDS-certified server, can we hire your experts to handle or oversee the migration process?

hot flax
#

@rugged nimbus Yes — when you export a project, you do get the full source code (frontend + backend), and the code itself is portable and standard with no proprietary dependencies or phone-home logic.

That said, at the moment, apps built on Emergent.sh are intended to run on Emergent-managed infrastructure only. The platform don’t currently support running or deploying these apps on external or self-hosted environments, including third-party or HDS-certified infrastructure.