ORBYT 2.0
Welcome Sign in β–Ύ Register
← Back

Explore our pages

Find what you need in our site pages.

// philosophy

Platform Philosophy

Choose software by its actual license, deployment options and support needs. Orbyt brings independent products and its own offerings into one marketplace.

Last updated 2026-10-17

A marketplace built around choice

Orbyt is built around a simple idea: customers should understand what they are buying, sellers should have room to present their work clearly, and software should be chosen based on how well it fits the user.

Orbyt brings independent software, hosted applications, digital services and Orbyt products into one marketplace with product listings, organization accounts, checkout, delivery and support tools.

The goal is not to force every product into the same model. Instead, Orbyt is designed to support different ways of building, buying, deploying and managing software.

Choice comes first

Different users need different things.

Some customers want a hosted service that is ready to use. Others want downloadable software they can install and control themselves. Some need team access, integrations, developer tools or specialized support.

Orbyt is designed to make those differences visible before purchase.

Depending on the product, you may find:

  • Hosted applications
  • Downloadable software
  • Self-hosted products
  • Subscription services
  • One-time purchases
  • Team and organization plans
  • Developer-focused tools
  • API-enabled products
  • Digital services
  • Products with multiple deployment options

The best option depends on your goals, infrastructure, technical experience and long-term needs.

Deployment and ownership

A product may be hosted, downloadable, self-hosted or available in more than one form.

Source-code delivery, installation rights, seat limits, updates, hosting responsibilities and support depend on the specific product and license.

Purchasing software does not automatically transfer copyright, provide unrestricted redistribution rights or guarantee unlimited installations.

A self-hosted product may give you greater control over infrastructure and deployment.

A hosted product may reduce local setup, maintenance and administration.

Neither model is automatically better.

The right choice depends on how much control, convenience, flexibility and responsibility you want.

Understand the license

Every software product has rules that define how it can be used.

Those rules may cover:

  • Number of users
  • Number of installations
  • Number of websites or domains
  • Commercial use
  • Internal business use
  • Source-code access
  • Modification rights
  • Redistribution
  • Updates
  • Support
  • Renewal requirements
  • Subscription terms
  • Transfer rights

Review the license before purchasing, especially when the software will be used for business-critical systems or deployed to multiple users, locations or customers.

For more information, read the licensing overview.

Clear information before purchase

Orbyt encourages sellers to provide enough information for customers to make informed decisions.

Before choosing a product or plan, review:

  • Publisher or seller
  • Product description
  • Features
  • Delivery method
  • Deployment options
  • Price
  • Billing interval
  • License scope
  • Compatibility
  • System requirements
  • Update policy
  • Support options
  • Third-party requirements
  • Available plans
  • Applicable limitations

If something is important to your workflow and is not clearly explained, ask before purchasing.

Compare more than price

Price is only one part of choosing software.

A lower-cost product may require more installation, maintenance or technical knowledge.

A hosted product may cost more over time but reduce the amount of infrastructure you need to manage.

A self-hosted product may offer greater control but also place more responsibility on your team.

When comparing products, consider:

  • Initial cost
  • Ongoing cost
  • Setup effort
  • Maintenance requirements
  • Hosting requirements
  • Technical knowledge
  • Support availability
  • Update frequency
  • Integration requirements
  • Long-term flexibility

Orbyt aims to give you the information needed to compare those tradeoffs.

Support should match the product

Support needs can vary just as much as software itself.

Some products may include direct seller support.

Others may offer documentation, community assistance, paid support plans or limited setup help.

Before purchasing, consider how important support is to your organization.

For critical systems, look closely at:

  • Support contact methods
  • Expected response times
  • Documentation
  • Installation assistance
  • Update support
  • Troubleshooting options
  • Developer support
  • Integration assistance

Independent sellers matter

Orbyt is designed to give independent sellers and developers a place to present, manage and grow their products.

Independent software can offer specialized solutions that may not exist in larger marketplaces.

Orbyt aims to make those products easier to discover while still giving customers enough information to evaluate them carefully.

Sellers remain responsible for accurately representing their products, licenses, requirements and support offerings.

Developers are part of the ecosystem

Orbyt is not only designed for customers purchasing finished products.

Developers can also use the platform to publish software, manage offerings, work with teams, explore integrations and build services around the wider Orbyt ecosystem.

The goal is to create a marketplace where developers can participate as builders, sellers and partners.

Teams should be able to manage access

Software is often purchased for more than one person.

Orbyt organization and team tools are designed to help businesses manage access without requiring every purchase to be tied to one individual workflow.

Depending on the product and plan, teams may be able to manage:

  • Members
  • Invitations
  • Roles
  • Product access
  • Seats
  • Workspaces
  • Administrative permissions

Actual capabilities depend on the selected product and plan.

Flexibility without hidden assumptions

Orbyt tries to avoid making assumptions about how software should be delivered.

A purchase should not automatically imply:

  • Lifetime support
  • Unlimited users
  • Unlimited installations
  • Source-code ownership
  • Permanent hosting
  • Automatic upgrades
  • Redistribution rights
  • Commercial resale rights

Those rights should come from the actual product listing and license.

Customers should know what happens next

The experience after purchase should be as clear as the purchase itself.

Depending on the product, delivery may include:

  • Immediate hosted access
  • Download access
  • License activation
  • Account provisioning
  • Team assignment
  • Setup instructions
  • Seller contact
  • Manual onboarding
  • Additional configuration

Review the listing so you know how the product will be delivered before completing checkout.

One-time purchases and subscriptions both have a place

Orbyt supports products sold through both one-time payments and recurring subscriptions.

A one-time purchase may be appropriate when the product is delivered once and ongoing service is limited.

A subscription may make more sense when a product includes hosting, continuous updates, ongoing infrastructure, support or regularly delivered services.

Neither pricing model is treated as universally better.

The product should explain what the customer receives and what continues for as long as payment remains active.

Transparency builds better software relationships

Orbyt believes a good software marketplace should make the relationship between customer and seller easier to understand.

Customers should know:

  • What they are buying
  • Who created it
  • How it is delivered
  • What the license allows
  • What support is included
  • What ongoing costs may exist
  • What dependencies are required

Sellers should have a clear way to explain those details.

Better information helps reduce confusion and creates better long-term relationships between customers, developers and software providers.

Built for an evolving ecosystem

Orbyt is designed to grow beyond a basic product catalog.

The wider ecosystem may include:

  • Orbyt Marketplace products
  • Independent sellers
  • Team and organization tools
  • Developer services
  • Orbytal media tools
  • OrbytX partnerships
  • Website integrations
  • APIs
  • Custom applications
  • Development and beta programs

Each part of the ecosystem can serve a different purpose while remaining connected through the same overall platform.

Our approach

Orbyt aims to support software that is easier to understand, easier to compare and easier to manage.

The philosophy is simple:

  • Give customers meaningful choices
  • Make important product information visible
  • Respect the actual software license
  • Support different deployment models
  • Give independent developers room to grow
  • Make team access easier to manage
  • Encourage clear seller communication
  • Avoid hidden assumptions
  • Help users choose based on fit, not just price

Explore Orbyt

Browse products

Read the licensing overview

Discuss a custom application

Choose the tools that fit your work. Understand what you are buying. Build with confidence.