Creating a Stack

A stack is a collection of tools and technologies that you use together. Share your stack to help others discover great tools and see how different technologies work together.

Before You Begin

To create a stack, you'll need a StackShare account. If you don't have one yet, you can sign up for free using your email or GitHub account.

Method 1: CLI Scanning (Recommended)

The fastest and most accurate way to create a stack is to scan your codebase with our CLI tool. It automatically detects the tools you're using from your project files, dependencies, and configuration.

Quick Start

npx stackshare scan

This will:

1. Analyze your project's package files, configs, and dependencies
2. Detect all the tools and technologies you're using
3. Create or update your stack on StackShare

Why Use CLI Scanning?

• Accurate - Detects tools from actual code, not memory
• Comprehensive - Finds tools you might forget to add manually
• Fast - Scan an entire project in seconds
• CI/CD Ready - Automate stack updates with your deployment pipeline

Learn more about CLI scanning →

Method 2: Manual Creation

If you prefer to build your stack manually or don't have a codebase to scan, you can create a stack through the web interface.

Step 1: Start a New Stack

Navigate to Create Stack from the navigation menu, or click the "Create Stack" option from your profile dropdown.

Step 2: Name Your Stack

Give your stack a descriptive name. This could be:

• A project name (e.g., "My SaaS App")
• A category (e.g., "Frontend Stack", "Data Pipeline")
• Your company name followed by a description

Step 3: Add Tools

Search for and add the tools you use. You can add tools from any category:

• Languages & Frameworks - JavaScript, Python, React, Django, etc.
• Data Stores - PostgreSQL, MongoDB, Redis, etc.
• DevOps - Docker, Kubernetes, GitHub Actions, etc.
• Business Tools - Slack, Notion, Linear, etc.
• AI - OpenAI, Anthropic, Hugging Face, etc.

Step 4: Add Descriptions (Optional)

For each tool, you can add a description explaining why you chose it and how you use it. This context is valuable for others who might be evaluating similar tools.

Step 5: Publish Your Stack

Once you're happy with your stack, publish it to make it visible to the community. You can always come back and edit it later.

Best Practices

• Keep it updated - Use CLI scanning in CI/CD to automatically update your stack
• Add context - Explain why you chose certain tools over alternatives
• Be honest - Include tools you actually use, not just aspirational ones
• Categorize well - Use appropriate categories for your tools