Applying the foundation to Ember

Use the whole definition

Ember is not a vendor alias

Ember brings multiple managed capabilities into a repeatable TDE pattern. It also includes the human and organizational system that makes those capabilities safe and usable.

Calling Ember only a PaaS or equating it with one provider hides important boundaries.

Current direction

Read each capability by supported purpose

The current confirmed direction places Render as the primary application interface and runtime, Supabase as managed backend capability, Vercel primarily on communications and documentation surfaces, Microsoft Entra for workforce identity context where applicable, and SendGrid as optional messaging.

That provider split is a platform direction. Exact application use still depends on purpose, data, configuration, and review.

Say what it does not mean

A supported platform is an enabling decision, not a universal answer

Ember does not mean every use of the named providers is approved. It does not make provider assurance equivalent to application assurance, and it does not permit unreviewed AI-generated changes.

The platform is strongest when its limits are easy to see and justified exceptions have a safe route.

• Application purpose and data remain explicit
• Authorization remains application-specific
• Production readiness requires evidence
• Exceptions require documented review