App Catalog
Browse curated one-click application stacks, review requirements, and deploy a complete app into an existing Skytells project.
The App Catalog is a curated collection of applications and complete service stacks that you can deploy into an existing Skytells project. Catalog entries are ready-to-run blueprints: choose an entry, review what it creates, select a project, and launch it through one guided flow.
Open App Catalog under Projects in the Console sidebar, or visit console.skytells.ai/app-catalog.
App Catalog is different from starter templates. A starter template forks source code into your GitHub account. A Catalog entry deploys a prepared application stack directly into your chosen project and does not require you to create a repository first.
Two Ways to Browse
Workspace catalog
Browse first, then choose the destination project. Use this when the application is your starting point.
Project catalog
Open a project and select its Catalog page. Use this when the destination project is already decided.
Both paths use the same catalog and deployment checks. The difference is when you select the project.
Deploy from the Catalog
Open App Catalog
Open the workspace catalog, or open Catalog from inside a project.
Search and Filter
Search by application name or purpose and use tags to narrow the results. Availability can differ by subscription tier.
Review the Application
Open an entry and review its description, included services, minimum plan, and any application-specific setup requirements. Multi-service entries are deployed as a coordinated Compose app.
Choose a Project
If you started from the workspace catalog, select a project where you have permission to create apps. From a project catalog, the destination is already selected.
Name and Deploy
Optionally customize the app name, then select Deploy. Keep the deployment overlay open while Skytells creates the application, applies the blueprint, and starts the first deployment.
Complete Application Setup
Open the new app, confirm its deployment reaches a ready state, and follow any application-specific first-run instructions. Add secrets or custom domains only through the app's protected settings.
Access and Plan Checks
A Catalog deployment can be unavailable for several distinct reasons:
| Check | What it means |
|---|---|
| Catalog availability | App Catalog must be enabled for the Console environment |
| Plan access | Your subscription must include one-click apps |
| Template tier | An individual application may require a higher tier |
| Project role | You need permission to create and deploy apps in the destination project |
| App limit | The destination project must have room for another app |
A Catalog entry can contain multiple containers while counting as a Compose app in the project. Review the included services and expected resource use before deploying to production.
After Deployment
Catalog apps use the standard app control surface. From the app page you can:
- inspect deployment history and build output;
- add environment variables and secrets;
- configure managed and custom domains;
- read runtime logs and monitoring;
- restart, redeploy, or change settings;
- manage every service in the Compose stack as one application boundary.
The Catalog controls how the initial stack is created. Day-to-day operations use the same App Overview and Deployments pages as other apps.
Catalog vs. Other Creation Methods
| Method | Best for | Source ownership |
|---|---|---|
| App Catalog | Deploying a curated complete app or multi-service stack | Prepared blueprint deployed directly |
| Starter template | Starting a codebase you intend to edit in GitHub | Forked repository belongs to you |
| Git import | Deploying an existing repository | You bring the repository |
| Docker image | Running a prebuilt image | You control the image source |
| Compose | Bringing your own multi-service definition | You provide the Compose configuration |
| Drop | Shipping a ZIP without connecting Git | You upload an archive |
Troubleshooting
The catalog is unavailable
The feature may not be enabled for the current environment or plan. Check the message shown in the Console and review your subscription.
An entry is visible but cannot be deployed
Check its minimum tier, your role in the destination project, and the project's app limit.
The first deployment fails
Open the app's deployment logs. Look for missing required environment variables, image pull errors, port conflicts, or application-specific initialization requirements.
The app deployed but is not ready to use
Some applications require a first-run account, token, or configuration step. Follow the entry's detail guidance and keep secrets in environment variables rather than source or Compose text.
Related
- Create an App — compare all app creation methods.
- App Types — understand how App Catalog launches become Compose apps with shared app controls.
- Starter Templates — fork an editable starter into GitHub.
- Drops — deploy directly from a ZIP archive using an app-derived architecture.
- Apps Overview — operate apps after deployment.
How is this guide?