Looking for Advice: Self-Hosting n8n for HIPAA Compliance on a Budget

Hello everyone,
I am looking for some guidance on how to productionize n8n for a healthcare project. Since we are dealing with protected health information (PHI), n8n cloud is not an option since we need full control over where our data is stored for HIPAA compliance.
Right now, it will just be a small team of five people collaborating to build and run the workflows. We want to keep costs reasonable while making sure the setup is secure and compliant.
We are open to either:

  • Running on our own physical servers on-premises and managing everything directly
    or
  • Using a HIPAA-compliant cloud service like AWS, if that makes more sense for cost and scaling
    I would love to get advice on:
    • Best way to host n8n while meeting HIPAA requirements.
    • Roughly how much it costs to run and maintain either option.
    • How others handle collaboration and deployment in production when working with a small team and deploying workflows to clients.
      If anyone has gone through this process or has ideas to share, I would greatly appreciate hearing about it.
      Thanks in advance!
1 Like

OK brother I think if you have this specific HIPAA-compliant configuration in AWS, you should use that and when you configure your n8n workflow try to make sure it is stateless and contains no persistent memory of client-specific details. What I mean is avoiding nodes like Conversation Memory

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.