Back to Platform Foundations
Draft complete9 minutes

Everyone who evaluates or relies on managed services

Cloud providers and service models

Understand what managed services take on, what customers configure, and why informal service labels need careful use.

The short answer

A cloud service model describes how responsibilities are divided. It does not guarantee that a particular use, configuration, or application is approved.

01

Name the right thing

Provider, service, platform, and application are different nouns

A provider is an organization. A service is a capability it operates. A platform combines capabilities into a supported experience. An application uses those capabilities for a specific outcome.

Contracts and architecture become confusing when these terms are treated as interchangeable.

Four related scopesEach layer answers a different question.
01ProviderWho offers the capability?
02ServiceWhat managed capability is offered?
03PlatformHow are capabilities made reusable?
04ApplicationWhat particular outcome is delivered?
02

Use formal models

IaaS, PaaS, and SaaS describe different control splits

Infrastructure as a Service exposes fundamental compute, storage, and network resources. Platform as a Service gives customers a supported application deployment environment. Software as a Service gives customers use of a provider-operated application.

Labels such as Backend as a Service can be useful industry shorthand, but they do not replace careful review of the actual service.

  • Which layers does the provider operate?
  • Which configuration does the customer control?
  • Who manages identity and data use?
  • What evidence and service commitments apply?
03

Managed is not ownerless

Work moves, but accountability remains

A managed database can remove operating-system patching from the application team while leaving schema design, access policies, data quality, and permitted use with the customer.

Always examine the actual service, plan, configuration, and contract instead of relying only on a category label.

Responsibility moves by layerManaged services reduce selected tasks without removing customer decisions.
01Provider operatesUnderlying service and contracted capability
02Platform enablesSupported pattern and reusable guardrails
03Application decidesPurpose, data, permissions, and logic

The Ember lens

Ember composes services from several providers and layers. It can offer a PaaS-like developer experience, but it is not one vendor service or one formal cloud service model.

Responsibility remains

Teams must review the actual responsibility split for each service and plan. A familiar category label is not evidence of a safe configuration.

Apply it

Map one managed service

Choose a service and divide five responsibilities between provider, Ember, and application team.

  1. 01Name the exact service and plan
  2. 02List provider-operated layers
  3. 03List customer configuration duties
  4. 04Identify evidence and escalation

Check your understanding

Make the ideas usable

2 questions
01What does a service-model label tell you?
02Who owns application authorization rules on a managed backend?

Source trace

Reviewable by design

Content owner: Wesley Almeida, Chief Technology Officer
Last reviewed: 2026-08-18

  • Ember Learn Platform Foundations05-projects/vibe-coding-platform/resources/learning/ember-learn-platform-foundations-course-2026-08-11.md
  • NIST SP 800-145