Deploy your first application

This quickstart takes the fastest path to a visible win: an application running on Facets. It is a linear procedure, not a tour. Each step links into the Platform Guide if you want the full picture.

Before you start

These are one-time setup steps, each covered elsewhere:

• A Facets tenant you can sign in to (Facets hosted or Self-hosted).
• The Praxis CLI installed and logged in. This quickstart uses raptor, the Praxis CLI binary that drives the control plane.
• A cloud account and a git account connected, so Facets can provision infrastructure and store your project's blueprint.

The example below uses a project called checkout, an environment called dev, and a service called web. Substitute your own names.

1. Import a project type

A new control plane starts empty, with no modules to build from. Import the official project type for your cloud to load a working catalogue in one command:

raptor import project-type --managed facets/aws

Run raptor import project-type --list-managed to see the other clouds. This is the one step with no console route on a fresh control plane. See Project Types for what a project type contains and how to adapt it.

2. Create a project

A project holds one blueprint of resources that you deploy across environments. Create one against the project type you just imported.

Create a project called checkout from the AWS project type.

# See the project types available to you and their names
raptor get project-types

# Create the project, passing the project type's name from above
raptor create project checkout --project-type "<project-type-name>" --description "Checkout service"

See Projects for blueprints, environments, and importing an existing repo.

3. Add a service and point it at an image

A service is how your application runs on Facets. Add one to the blueprint, then attach the container image it should run.

Add a service called web to checkout, then attach gcr.io/my-project/checkout:v1 to it in dev.

# See which service flavors your project type allows
raptor get resource-types --type service -p checkout

# Add a service to the blueprint
raptor apply resource service/<flavor>/<version> -n web -p checkout

# Point it at an image for the dev environment
raptor set artifact-uri -p checkout -e dev web --uri gcr.io/my-project/checkout:v1

To build images automatically from your branches instead of pinning one, see Attach image and CI/CD workflow.

4. Launch the environment

Before you can deploy, the environment has to be launched, which provisions its cloud infrastructure (network, cluster, storage) from your blueprint. Launch bootstraps that infrastructure without deploying your resources yet.

Create and launch an environment called dev in checkout.

raptor create environment dev -p checkout --launch -w

# If the environment already exists but is stopped, launch it instead
raptor launch environment dev -p checkout -w

5. Deploy your application

A release applies your blueprint to the launched environment, deploying the service and its image.

Release checkout to dev and wait for it to finish.

raptor create release -p checkout -e dev -w

See Releases for selective and custom releases, plans, and rollout strategies.

6. Confirm it is running

When the release finishes, the environment shows as Running. Open the Resource Center (or the Environment Overview) to see your web service live, with its status, logs, and metrics.

To make the application reachable on a custom domain, add an ingress resource, map the domain, and add the CNAME record at your DNS provider. See Exposing to the internet.

You now have a running application

That is the whole path: an imported catalogue, a project, a service pointed at an image, a launched environment, and a release that put it on your cloud. To go deeper:

• Project Types: what a project type bundles and how to shape your own.
• Projects: blueprints, environments, and resources.
• Releases: how deployments plan, apply, and promote.