Looking for guidance on pushing Dev Tier (multi-tenant, clean architecture)

Hi @graceanli ,

Welcome to the Community, and thanks for creating a Developer Tier account.

Let me see if I can answer some of your questions, especially those related to the Developer Tier offering.

Dev Tier feasibility: In practice, can Dev Tier support strong multi-tenant isolation (e.g., per-tenant namespaces/workspaces, RLS patterns, separated service principals)? Or are there common blockers that typically require Enterprise?

Foundry is designed from the ground up for exactly this; it’s central to how many of our customers use Foundry! One of the main ways security is enforced is through Organizations and Spaces. However, Developer Tier does not support more than one Organization - this is only available to paying customers. You can however create multiple Spaces.

Limits to plan around: Any Dev Tier caps that could constrain this approach?

You can find more information about the limits of Developer Tier in this post - https://community.palantir.com/t/queries-regarding-free-tier-developer-account/5073 .

Learning path: Recommended training/certs for a solo builder beyond Speedruns?

Absolutely! Would recommend checking out the complete learning track for the profile that most suits you.

Also, subscribe to our “Palantir Developers” YouTube channel for the latest from our builders and product teams.

Design for minimal rework: If starting on Dev Tier, what early design choices help a future migration (naming/namespace strategy, per-tenant isolation approach, repo/port-adapter boundaries, approval workflows, logging/audit strategy)?

I’m sure the Community will have a lot more to add here, but as a starter please be sure to checkout our best practice guides in the docs. For example.

Also, note that should you upgrade to Enterprise, you will not necessarily need to migrate to a new account. We can upgrade your Developer Tier account if you wish.