Seeking Best Practices for Single-Enterprise & Multi-Tenant Foundry Configurations

Hello fellow Palantir Foundry developers and experts,

My team is currently working on establishing our organization’s setup and configuration in Palantir Foundry, and we want to ensure we’re building on a solid foundation. We have immediate needs for a single-company setup, but we are also planning for a multi-tenant deployment in the near future.

While we have working implementation currently in place, we have the distinct feeling that we might be reinventing the wheel or making things much harder than they need to be and would be incredibly grateful for any guidance or best practices from those who have more experience.

Specifically, we are trying to find:

  1. A Reference Setup for a Single Enterprise:
  • What are the recommended best practices for structuring projects, folders, and datasets for a single company to ensure scalability and ease of use?
  • Are there any documented or community-accepted reference architectures for how to handle data ingestion, transformation, and ontology development in this context?
  1. A Reference Setup for a Multi-Tenant Deployment:
  • How do best practices differ when configuring Foundry for multiple tenants? What are the key considerations for ensuring strict data isolation and security between tenants?
  • What are the most effective ways to manage user roles and permissions across different tenant organizations?
  1. Scripted or Automated Configurations:
  • Has anyone in the community developed or is anyone aware of scripted examples (e.g., using foundry-cli, APIs, or other tools) for setting up either of these configurations? Having a template or a scripted starting point would be immensely helpful for us.

We are trying to avoid common pitfalls and establish a robust, scalable, and secure Foundry environment. Any advice or examples of how your organization has tackled this would be greatly appreciated.

Thank you in advance for sharing your expertise!