message: Add doc on available services
diff: ---
  title: Available Fluid services
  menuPosition: 1
  -status: unwritten
  ---
  -Overview of the available Fluid services and the differences.
  +The Fluid Framework can be used with any compatible service implementation. Some services, like Tinylicious, are
  +intended only for testing and development, while other hosted options provide the high scalability needed for
  +production-quality applications.
  -- Tinylicious
  -- Azure Fluid Relay service
  -- DIY R11s
  +## Tinylicious
  +
  +[Tinylicious]({{< relref "tinylicious.md" >}}) is a minimal, self-contained implementation of the Fluid Framework
  +service that is much smaller (tinier!) than Routerlicious, the reference implementation of the service.
  +
  +Tinylicious is intended for testing and development only.
  +
  +{{% callout tip %}}
  +
  +The easiest way to try out Fluid is with Tinylicious or Azure Fluid Relay.
  +
  +{{% /callout %}}
  +
  +## Azure Fluid Relay
  +
  +Microsoft Azure Fluid Relay is a hosted Fluid service. You can provision Fluid Relay services as part of your
  +Microsoft Azure subscription and use the [@fluidframework/azure-client]({{< relref "azure-client.md" >}}) library to
  +create and load Fluid containers.
  +
  +{{% callout important %}}
  +
  +Azure Fluid Relay is currently in *Private Preview*.
  +
  +{{% /callout %}}
  +
  +## Self-hosted Routerlicious
  +
  +Fluid Framework's original service implementation, called [Routerlicious][r11s], is part of the Fluid Framework open source
  +project. Routerlicious is not formally supported as a production-quality service, but you can run it using Docker. See
  +the [Routerlicious readme][r11s] for more information about running it.
  +
  +[r11s]: https://github.com/microsoft/FluidFramework/tree/main/server#readme
  