NetBurner 3.5.6
PDF Version
Custom Branding

Custom Branding

Overview

NetBurner is an OEM (Original Equipment Manufacturer) that enables complete customization of our products to align with your brand identity. Whether you need simple logo changes or comprehensive white-label solutions, NetBurner provides the flexibility to present your brand to your customers seamlessly.

Branding Capabilities Options

Custom branding options include:

  • Configuration Server web page logo
  • Custom web page user interface
  • Physical label customization using NetBurner label template
  • NetBurner application utilities branding
  • Private cloud server to replace discover.netburner.com

Customization Options

1. Configuration Server Logo Replacement

Replace the NetBurner logo on configuration screens with your company branding.

Default Configuration Page Custom Branded Page
┌─────────────────────────┐ ┌─────────────────────────┐
│ [NetBurner Logo] │ │ [Your Company Logo] │
│ │ ────> │ │
│ Device Configuration │ │ Device Configuration │
│ ┌──────────────────┐ │ │ ┌──────────────────┐ │
│ │ Network Settings │ │ │ │ Network Settings │ │
│ └──────────────────┘ │ │ └──────────────────┘ │
└─────────────────────────┘ └─────────────────────────┘

Implementation:**

  • Reference the CustomWebConfigSystem example
  • Replace logo image file
  • Update HTML references

  • Rebuild and deploy

    Location:** See example in NNDK examples directory

2. Custom Configuration Interface

Create a fully branded configuration interface integrated into your application.

Application Architecture
┌──────────────────────────────────────────────────┐
│ Your Application │
│ │
│ ┌─────────────────┐ ┌──────────────────┐ │
│ │ Custom Web UI │ │ Application │ │
│ │ • Your branding│ <──> │ Logic │ │
│ │ • Your style │ │ │ │
│ └────────┬────────┘ └──────────────────┘ │
│ │ │
│ v │
│ ┌─────────────────────────────────────────┐ │
│ │ NetBurner Configuration API │ │
│ │ • Read settings │ │
│ │ • Modify settings │ │
│ │ • Save to persistent storage │ │
│ └─────────────────────────────────────────┘ │
└──────────────────────────────────────────────────┘
│
v
[Hardware Settings]

Key Points:**

  • The default configuration server is optional
  • Your application has full access to all configuration settings

  • Settings can be modified via:

    • Custom web interface
    • Application code directly
    • REST APIs
    • Command protocols

    Example Location:**

<NNDK_ROOT>/examples/web/
Typically /nburn/examples/web/

Capabilities:**

  • Display current settings
  • Modify any configuration parameter
  • Save changes to persistent storage
  • Apply changes at runtime

3. Physical Device Labeling

Order NetBurner hardware without NetBurner branding.

Standard Label Custom Label
┌───────────────────────┐ ┌───────────────────────┐
│ │ │ │
│ [NetBurner Logo] │ │ [Your Logo Here] │
│ │ ─────> │ │
│ Model: MOD5441X │ │ Model: YOUR-MODEL │
│ S/N: 12345 │ │ P/N: YOUR-PART-NUM │
│ MAC: 00:03:F4:... │ │ S/N: 12345 │
│ │ │ MAC: 00:03:F4:... │
└───────────────────────┘ └───────────────────────┘

Options:**

  1. No Label: Order devices without any NetBurner label

  2. Custom Label: Use NetBurner-provided templates to create labels with:

    • Your company logo
    • Your part numbers
    • Your branding elements
    • Required regulatory markings

    Process:**

  1. Contact NetBurner sales for label templates
  2. Design your custom label
  3. Submit for approval
  4. Order devices with custom labels

4. Discovery Utility Customization

Rebrand NetBurner PC utilities to match your company identity.

Discovery Tool Workflow
┌─────────────────────────────────────────────────────────┐
│ Your Branded Utility │
│ │
│ ┌──────────────┐ ┌──────────────┐ │
│ │ Network │ -----> │ Device │ │
│ │ Scanner │ │ List │ │
│ └──────────────┘ └──────────────┘ │
│ │ │ │
│ v v │
│ ┌──────────────────────────────────────┐ │
│ │ Device Communication │ │
│ │ • Discovery protocol │ │
│ │ • Configuration access │ │
│ │ • Firmware updates │ │
│ └──────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────┘

Available Tools:**

Utility Function Customization Level
localdiscover Find devices on local network Full source available
find Device discovery tool Full source available
Additional tools Various utilities Source provided

Source Location:**

<NNDK_ROOT>/pctools/

Customization Capabilities:**

  • Change application name and branding
  • Modify user interface
  • Add custom functionality
  • Integrate with your systems

  • Deploy with your software packages

    Build Process:**

  1. Locate source in pctools directory
  2. Modify branding elements
  3. Update strings and resources
  4. Compile for target platform
  5. Distribute with your product

5. Custom Cloud Server Infrastructure

Difficulty:** Expert

Replace discover.netburner.com with your own cloud infrastructure.

Default Architecture Custom Architecture
┌──────────────┐ ┌──────────────┐
│ Device │ │ Device │
│ │ │ │
└──────┬───────┘ └──────┬───────┘
│ │
│ HTTPS │ HTTPS
v v
┌──────────────┐ ┌──────────────┐
│ discover. │ ========> │ your-cloud. │
│ netburner. │ │ your-domain. │
│ com │ │ com │
└──────┬───────┘ └──────┬───────┘
│ │
v v
┌──────────────┐ ┌──────────────┐
│ Client │ │ Client │
│ Apps │ │ Apps │
└──────────────┘ └──────────────┘

Requirements:**

Infrastructure:**

  • Cloud hosting platform (AWS, Azure, GCP, etc.)
  • SSL/TLS certificates
  • Domain name and DNS configuration
  • Load balancing (for production)
  • Database for device registry

  • API endpoints for device communication

    Protocol Implementation:**

  • Device discovery protocol
  • Secure authentication
  • Registration and management
  • Status monitoring
  • Firmware update distribution

  • Client application APIs

    Architecture Components:**

Cloud Server Stack
┌─────────────────────────────────────────────┐
│ Client Applications │
│ (Web, Mobile, Desktop) │
└───────────────────┬─────────────────────────┘
│ REST/WebSocket
v
┌─────────────────────────────────────────────┐
│ API Gateway / Load Balancer │
└───────────────────┬─────────────────────────┘
│
┌───────────┴───────────┐
v v
┌───────────────┐ ┌───────────────┐
│ Device │ │ User │
│ Management │ │ Interface │
│ Service │ │ Service │
└───────┬───────┘ └───────┬───────┘
│ │
└───────────┬───────────┘
v
┌───────────────────────┐
│ Device Database │
│ • Registry │
│ • Status │
│ • Configuration │
└───────────────────────┘

Security Considerations:**

  • Device authentication tokens
  • Encrypted communications
  • Access control and permissions
  • Audit logging

  • Compliance requirements

    Warning:** This is an advanced customization requiring:

  • Strong backend development skills
  • Cloud infrastructure expertise
  • Security best practices knowledge
  • DevOps capabilities
  • Ongoing maintenance commitment

Implementation Strategy

Planning Your Customization

Step 1: Assess Requirements
│
v
┌─────────────────────────┐
│ What level of branding │
│ does your product need? │
└───────────┬─────────────┘
│
v
Step 2: Choose Approach
│
┌──────┴──────┐
v v
┌────────┐ ┌────────┐
│ Simple │ │Complex │
│ Quick │ │Custom │
└───┬────┘ └───┬────┘
│ │
v v
Logo/Label Full Custom
Changes Infrastructure

Recommended Path

Phase 1 - Quick Wins (Week 1)**

  1. Change configuration server logo
  2. Order devices with custom labels

  3. Update application name and strings

    Phase 2 - Custom Interface (Week 2-3)**

  1. Design custom web UI
  2. Implement configuration interface
  3. Add your branding elements

  4. Test thoroughly

    Phase 3 - Utilities (Week 4)**

  1. Customize discovery tools
  2. Update PC utilities
  3. Rebrand documentation

  4. Package for distribution

    Phase 4 - Advanced (Month 2+)**

  1. Plan cloud infrastructure (if needed)
  2. Implement custom services
  3. Migrate devices
  4. Monitor and maintain

Best Practices

Visual Consistency

Ensure brand consistency across all touchpoints:

Brand Touchpoints
Device Label <───> Web Interface <───> PC Utilities <───> Cloud Portal
│ │ │ │
v v v v
Your Logo Your Colors Your Name Your Brand
Your P/N Your Fonts Your Icon Your Domain

Configuration Access Patterns

┌─────────────────────────────────────────────────────┐
│ Configuration Data Flow │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Web UI │ │ API │ │ Direct │ │
│ │ │ │ │ │ Code │ │
│ └────┬─────┘ └────┬─────┘ └────┬─────┘ │
│ │ │ │ │
│ └─────────────────┴─────────────────┘ │
│ │ │
│ v │
│ ┌───────────────────────────────┐ │
│ │ Configuration API Layer │ │
│ └───────────────┬───────────────┘ │
│ │ │
│ v │
│ ┌───────────────────────────────┐ │
│ │ Persistent Storage │ │
│ └───────────────────────────────┘ │
└─────────────────────────────────────────────────────┘

Testing Checklist

  • Logo displays correctly on all screens
  • All text reflects your branding
  • Custom utilities function properly
  • Configuration changes persist across reboots
  • Discovery tools find your devices
  • Documentation references your brand
  • Physical labels are accurate
  • Cloud services (if applicable) are operational

Resources and Support

Example Code Locations

Customization Type Location Description
Configuration Logo CustomWebConfigSystem Logo replacement example
Custom Web Interface <NNDK_ROOT>/examples/web/ Web-based configuration
PC Utilities Source <NNDK_ROOT>/pctools/ Discovery and management tools

Getting Started

For Simple Customizations:**

  1. Review the CustomWebConfigSystem example
  2. Prepare your logo files (PNG, SVG formats)
  3. Follow example documentation

  4. Test on development device

    For Complex Customizations:**

  1. Contact NetBurner technical support
  2. Discuss your requirements
  3. Review available options
  4. Plan implementation timeline

Support Channels

  • Technical Documentation: NetBurner NNDK documentation
  • Example Code: Examples directory in NNDK
  • Technical Support: NetBurner support team
  • Community Forums: NetBurner developer community

Security Considerations

When implementing custom branding, maintain security:

Security Layers
┌─────────────────────────────────────┐
│ Your Branded Interface │ < Authentication
├─────────────────────────────────────┤
│ Configuration Access │ < Authorization
├─────────────────────────────────────┤
│ Device Communication │ < Encryption
├─────────────────────────────────────┤
│ Cloud Services (if any) │ < Secure Channels
└─────────────────────────────────────┘

Key Principles:**

  • Maintain authentication mechanisms
  • Preserve encryption protocols
  • Don't expose sensitive configuration
  • Validate all user inputs
  • Log security-relevant events
  • Keep firmware update security intact

Quick Decision Matrix:**

Your Needs Recommended Approach
──────────────────────────────────────────────────────
Simple logo change > Configuration logo replacement
Custom look and feel > Custom web interface
Complete white label > All customization options
Enterprise deployment > Custom cloud infrastructure
Time-to-market priority > Start with logo, iterate
Full control requirement > Complete customization path

Start with simple customizations and expand as your product evolves and requirements grow.