Skip to main content

Marketplace Prerequisites

Before submitting your application for Armada Edge Platform marketplace certification, you must complete all prerequisites outlined in this guide.

Partner Agreement Requirements

Partner Account Registration

Complete the partner onboarding process:

partner_registration:
required_steps:
- company_verification: true
- legal_agreements: true
- tax_documentation: true
- contact_information: true
- technical_contact: true

Required Documentation:

  • Company registration certificate
  • Tax identification documents
  • Legal entity verification
  • Authorized signatory information

Compliance Requirements

Meet all legal and compliance requirements:

compliance_requirements:
legal:
- terms_of_service: true
- privacy_policy: true
- data_processing_agreement: true
- intellectual_property_rights: true

regulatory:
- export_controls: true
- data_residency: true
- industry_specific_regulations: true

Terms of Service

Accept and comply with marketplace terms:

marketplace_terms:
- service_level_agreements: true
- support_commitments: true
- update_notification_policy: true
- security_requirements: true
- intellectual_property_protection: true

Application Metadata Setup

Basic Application Information

Required application metadata:

application_metadata:
app_name: "Your Application Name" # Display name on marketplace
version: "1.2.0" # Semantic versioning
publisher_name: "Your Company Name" # Company display name
industry_categories:
- "Oil & Gas"
- "Manufacturing"
- "Healthcare"
- "Retail"
- "Other"

description: |
Brief description of your application (max 500 characters)

long_description: |
Detailed description of your application features and capabilities

release_notes: |
- New feature: Enhanced data processing
- Bug fix: Resolved authentication issue
- Performance: Improved response times

Contact Information

Provide complete contact details:

contact_information:
primary_contact:
name: "John Doe"
title: "Technical Lead"
email: "john.doe@company.com"
phone: "+1-555-123-4567"

support_contact:
name: "Jane Smith"
title: "Support Manager"
email: "support@company.com"
phone: "+1-555-987-6543"

business_contact:
name: "Bob Johnson"
title: "Business Development"
email: "bob.johnson@company.com"
phone: "+1-555-456-7890"

Application Assets

Required application assets:

application_assets:
logo:
format: "PNG"
size: "512x512 pixels"
background: "Transparent"
file_size: "< 1MB"

screenshots:
- format: "PNG"
size: "1920x1080 pixels"
description: "Main dashboard"
- format: "PNG"
size: "1920x1080 pixels"
description: "Configuration panel"
- format: "PNG"
size: "1920x1080 pixels"
description: "Analytics view"

documentation:
- installation_guide: "PDF or Markdown"
- user_manual: "PDF or Markdown"
- api_documentation: "OpenAPI/Swagger"
- troubleshooting_guide: "PDF or Markdown"

Support Agreements

Support Level Definitions

Define support tiers and response times:

support_levels:
standard_support:
response_time: "24 hours"
availability: "Business hours (9 AM - 5 PM EST)"
channels: ["Email", "Support portal"]
included_features:
- "Documentation access"
- "Community forums"
- "Email support"

premium_support:
response_time: "4 hours"
availability: "24/7"
channels: ["Email", "Phone", "Support portal", "Slack"]
included_features:
- "Priority ticket handling"
- "Phone support"
- "Dedicated support engineer"
- "Custom integrations"

enterprise_support:
response_time: "1 hour"
availability: "24/7"
channels: ["Email", "Phone", "Support portal", "Slack", "On-site"]
included_features:
- "Dedicated account manager"
- "Custom development"
- "On-site support"
- "Training and workshops"

Escalation Process

Define issue escalation procedures:

escalation_process:
level_1:
duration: "4 hours"
action: "Initial response and triage"
team: "Support team"

level_2:
duration: "8 hours"
action: "Technical investigation"
team: "Senior support engineer"

level_3:
duration: "24 hours"
action: "Engineering team involvement"
team: "Development team"

level_4:
duration: "48 hours"
action: "Management escalation"
team: "Product management"

Technical Prerequisites

Development Environment

Ensure your development environment is ready:

development_environment:
required_tools:
- name: "Docker"
version: "20.10+"
purpose: "Container building and testing"

- name: "kubectl"
version: "1.20+"
purpose: "Kubernetes deployment testing"

- name: "Helm"
version: "3.8+"
purpose: "Chart packaging and deployment"

- name: "Trivy"
version: "0.40+"
purpose: "Security scanning"

testing_environment:
- kubernetes_cluster: "Local or cloud-based"
- container_registry: "Access to push images"
- helm_repository: "Access to publish charts"

Security Requirements

Meet security prerequisites:

security_prerequisites:
vulnerability_scanning:
- tool: "Trivy, Clair, or Snyk"
- frequency: "Before each release"
- threshold: "No critical or high vulnerabilities"

image_signing:
- tool: "Cosign or Docker Content Trust"
- requirement: "All images must be signed"

sbom_generation:
- format: "CycloneDX or SPDX"
- requirement: "Must be included with submission"

Financial Prerequisites

Revenue Sharing Agreement

Understand revenue sharing model:

revenue_sharing:
marketplace_fee: "15% of gross revenue"
payment_terms: "Net 30 days"
payment_method: "Wire transfer or ACH"

reporting:
- frequency: "Monthly"
- format: "CSV or API"
- details: "Sales, refunds, adjustments"

Pricing Model

Define your pricing strategy:

pricing_model:
license_types:
- name: "Per Core"
description: "Licensed per CPU core"
pricing: "$100 per core per month"

- name: "Per Instance"
description: "Licensed per deployment"
pricing: "$500 per instance per month"

- name: "Subscription"
description: "Unlimited usage"
pricing: "$2000 per month"

billing_frequency:
- monthly: true
- annual: true
- custom: "Contact sales"

Intellectual Property

Ensure IP protection:

intellectual_property:
ownership:
- confirm_ownership: true
- third_party_licenses: "Documented"
- open_source_components: "Listed"

licensing:
- license_type: "Proprietary, Open Source, or Dual"
- license_terms: "Clearly defined"
- usage_restrictions: "Specified"

Data Protection

Comply with data protection requirements:

data_protection:
privacy_compliance:
- gdpr: "If applicable"
- ccpa: "If applicable"
- industry_specific: "HIPAA, SOX, etc."

data_handling:
- data_collection: "Minimal and documented"
- data_processing: "Secure and compliant"
- data_retention: "Defined policies"
- data_deletion: "User rights respected"

Submission Prerequisites Checklist

Pre-Submission Checklist

Complete all items before submission:

prerequisites_checklist:
partner_agreement:
- [ ] Partner account registered
- [ ] Legal agreements signed
- [ ] Compliance requirements met
- [ ] Terms of service accepted

application_metadata:
- [ ] Application name and version defined
- [ ] Publisher information complete
- [ ] Industry categories selected
- [ ] Description and release notes written
- [ ] Contact information provided
- [ ] Application assets prepared

support_agreements:
- [ ] Support levels defined
- [ ] Response times specified
- [ ] Escalation process documented
- [ ] Support contacts identified

technical_prerequisites:
- [ ] Development environment ready
- [ ] Security scanning configured
- [ ] Image signing setup
- [ ] SBOM generation working

financial_prerequisites:
- [ ] Revenue sharing agreement understood
- [ ] Pricing model defined
- [ ] Payment terms agreed

legal_prerequisites:
- [ ] IP ownership confirmed
- [ ] Licensing terms defined
- [ ] Data protection compliance verified

Validation Process

Pre-submission validation:

# Validate prerequisites
./validate-prerequisites.sh

# Check all requirements
./check-requirements.py

# Generate validation report
./generate-report.py > prerequisites-report.json

Next Steps

Once all prerequisites are completed:

  1. Review Checklist: Ensure all items are checked
  2. Validate Requirements: Run validation scripts
  3. Prepare Package: Create application package
  4. Submit Application: Begin certification process

For questions about prerequisites, contact: