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

Ask the Community
1

Context (high level)

  • Solo builder, early in the build.

  • Completed Speedruns; limited hands-on beyond that.

  • Goal: set a clean architecture now to avoid rework later.

What I’m aiming to do (kept intentionally generic)

  • Multi-tenant SaaS on Foundry with strict tenant isolation.

  • Ontology-centric reads; Actions for all writes.

  • Orchestrated background workflows (no customer data included here).

  • Analytics layer + optional AI-assisted recommendations that always require an admin approval step (no auto-execution).

  • External app ↔ Foundry via OAuth2 + REST.

Questions:

  1. 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?

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

    • Ontology scale (objects, relationships, versioning)

    • Actions throughput, idempotency/audit patterns

    • Automate / scheduled jobs / event triggers

    • AIP Logic/Agents availability or constraints

    • API/webhook rate limits or external integration boundaries

  3. 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)?

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

  5. Early-stage pathways: Any programs or suggested paths for projects that may need select Enterprise-only capabilities before fully committing?

1 Like
2

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.

1 Like
3

Thank you for the response. It seems like it would make the most sense for me to go and upgrade to Enterprise. I reached out to someone about upgrading to Enterprise about a week ago but haven’t heard back. Is there a certain timeframe I should expect or plan for the process of upgrading to Enterprise?

4

Hi @graceanli ,

I would encourage you to really explore the limits of Developer Tier first. There’s a lot you can do there.

If that doesn’t work, you’ll find the option to enquire about upgrading in the “Your Plan” page in Control Panel, or you can reach out via our website.

Thanks!

1 Like
5

Hi,

Thank you again for the clarification and recommendations around Organizations vs. Spaces, and for confirming that Developer Tier supports only a single Organization.

I reached out about upgrading to Enterprise a month ago but haven’t received a response yet, so I’m continuing to move forward on Dev Tier in the meantime. I want to sanity-check that I’m not missing a clear temporary pattern or workaround.

My current goal is to run a limited (two-tenant) real multi-tenant, multi-user SaaS on Dev Tier, while also designing and validating a multi-tenant-ready architecture (strict tenant isolation, ontology-centric reads, Actions for writes, etc.) so that a future move to an Enterprise deployment requires minimal rework.

With that in mind, I’m currently considering this approach:

  • Model each “tenant” as its own Space within the single Organization on Dev Tier.

  • Use ontology, markings, and data modeling patterns to enforce clear logical separation.

  • Have a small number of internal users acting as stand-ins for multiple external tenants.

Where I’m running into questions are these two points:

1. 5-user limit on Dev Tier
Given the 5-user cap, is the pattern above (multiple Spaces, one Organization, a handful of internal users simulating multiple tenants) the intended or recommended way to design and test a multi-tenant architecture on Dev Tier?
Or is there a better pattern you’ve seen teams use to validate multi-tenant isolation and workflows before upgrading?

2. No custom homepages on Dev Tier
Since custom homepages are not available, what are the recommended ways at Dev Tier to approximate a per-tenant “entry point” or guided experience?
For example, is the typical approach to rely on specific applications, saved views, or a particular Workshop/Contour pattern to give each Space something homepage-like, even if it’s not a true custom homepage?

I’ve reviewed the Dev Tier docs and related community posts, but I haven’t seen a clear description of best practices for simulating a multi-tenant SaaS on Dev Tier while preparing for an eventual Enterprise upgrade.

Any concrete recommendations or examples for this transitional pattern would be very helpful.