🧪Creating Your First Project

Before you can issue licenses, validate usage, or restrict environments, you need a Project. A project is the “container” for everything DevPayr manages on your behalf — licenses, domains, metadata, injectables, API keys, and more.

Think of it like a folder in your workspace: every software you build gets its own folder so things don’t get messy. DevPayr works the same way.

Let’s walk through the process properly.

🧠 What Exactly Is a Project?

A Project in DevPayr represents one digital product you want to protect. This can be:

• A full SaaS platform

• A client website or dashboard

• A mobile app

• A plugin, package, or library

• A theme or template

• A private internal tool

• A multi-environment system (local → staging → production)

Each project has its own:

• Licenses

• API keys

• Domains

• Injectables

• Usage limits

• Custom metadata

• Validation rules

This separation allows you to manage multiple apps under one DevPayr account without mixing their configuration.

💡 Tip: If you’re wondering whether something should be a separate project, the rule of thumb is simple: If the product is sold, installed, or deployed independently, it should be its own project.

🛠️ Step-by-Step: Creating Your First Project

Follow these steps inside your DevPayr dashboard:

1. Log into your DevPayr dashboard

Your dashboard is where all project creation and management happens.

2. Navigate to the “Projects” section

This page lists every project you’ve created so far.

From here, you can:

• View existing projects

• Edit them

• Delete them

• Or move on to creating a new one

3. Click “Create New Project”

This opens the project creation form.

You’ll see a few fields — nothing complicated. Let’s go through them.

🔤 Project Name

Give your project a name that makes sense to you.

Examples:

• DevPayr Storefront

• Client A – Contractor Platform

• Inventory App v2

• BeautySalonTemplate

• MyAmazingSaaS

This name appears everywhere: your dashboard, your APIs, your SDK logs, and your webhooks.

💡 Tip: You can rename the project anytime. DevPayr does not freeze the name in stone or engrave it on the blockchain.

🗂️ Project Description (Optional)

This helps you remember the purpose of the project — especially useful if you manage many apps.

Examples:

• “E-commerce storefront for client fashion brands.”

• “Internal tool for team attendance.”

• “Custom booking system for beauty salons.”

Not required — but helpful.

🧩 Meta Data (key : value) — Optional but Powerful

This is where DevPayr gives you superpowers. You can attach custom metadata to a project in the form of simple key:value pairs.

Anything added here:

• Shows up in every API response

• Shows up in every webhook payload

• Helps you track internal data without needing another system

• Can store customer identifiers, billing references, plan codes, etc.

Examples:

Key	Value
client_id	382912
plan	“premium-annual”
region	“EU-West”
internal_tag	“phase3-launch”

💡 Tip: Use metadata to seamlessly tie DevPayr’s licensing events into your billing platform, CRM, or analytics system.

🌍 Domains (optional for now)

You can set domains later, but here’s why this matters:

• Linking a domain ensures only that domain can run the software

• You can restrict licenses to specific domains

• You can enforce production vs testing environments

• It helps in tracking paid / unpaid deployments

If you're not ready to add domains, skip it for now — you’ll configure it after creating the project.

🎯 Final Step: Click Create Project

Once you click the button:

• Your project becomes active

• You can now generate licenses

• You can attach API keys

• You can configure environments

• You can upload injectables

• And you can start validating installations

You’ve officially entered the DevPayr universe 🎉

🧭 After Creating a Project — What’s Next?

Here’s what most users do right after project creation:

1. Create your first license

This is what your application will validate.

2. Add domains (optional but recommended)

Especially for SaaS apps and client websites.

3. Generate an API key (optional)

Only if you want advanced programmatic access.

4. Test your validation workflow

Use the SDK or raw HTTP to confirm everything works.

📝 Best Practices for Project Organization

• One product = One project Don’t mix five client apps inside one project — licensing will get confusing.

• Name projects clearly Future you will appreciate this.

• Use metadata wisely It’s extremely powerful for automation, billing, and internal tracking.

• Add domains early Helps avoid situations where your client deploys on 12 unknown URLs.

🎉 Congratulations!

You’ve just created your first DevPayr project — the foundation of everything else you will do.