Development / Beta Program

Help shape the next release

The Orbyt Development / Beta Program gives approved users early access to selected products, features, integrations, and services that are still being tested or prepared for public release.

Products marked Development / Beta may accept applications for early access.

You can apply using your personal Orbyt workspace or an eligible team workspace that you own or administer. Applications are reviewed before access is granted, and approval is not automatic.

Participation may be limited based on the product, testing goals, available seats, technical requirements, region, account standing, or the type of feedback currently needed.

Who can apply

The program is designed for users who are willing to actively test upcoming Orbyt products and provide useful feedback.

Depending on the beta, we may be looking for:

• Individual users
• Independent developers
• Software sellers
• Media developers
• Business owners
• Teams and organizations
• Website and API developers
• Existing Orbyt customers
• Users with specific workflows, platforms, devices, or technical environments

Some beta programs may have additional eligibility requirements listed on the product page.

How applications work

When you apply, you may be asked to provide information about how you plan to use the product, your organization, your technical environment, or the type of testing you can provide.

Submitting an application does not guarantee approval.

If approved, your account will show the beta access granted to you, including any applicable seat limits, workspace assignment, access period, or special instructions.

You may also receive additional information about setup, testing priorities, known limitations, or features we would especially like feedback on.

Your access

Beta approval may include access for a specific period, a limited number of seats, or a specific workspace.

Your approval determines the actual access granted to your account.

Access may:

• Begin immediately after approval
• Start on a scheduled date
• Be limited to selected features
• Be restricted to a personal or team workspace
• Include a limited number of users or seats
• End automatically on a specified date
• Continue until the beta program closes
• Change as the product moves through development

Beta access is separate from a normal purchase or subscription unless specifically stated otherwise.

Applying for or participating in a beta does not automatically create a paid subscription, product purchase, or license.

Beta access after release

Some approved testers may be allowed to keep access after the product officially launches at no additional charge.

This may be offered as a thank-you for meaningful participation, testing, or feedback.

However, continued access is not guaranteed.

If continued access is offered, the applicable product, plan, number of seats, duration, and any other conditions will be shown in your account or communicated to you directly.

A beta grant should never be assumed to provide permanent ownership, a lifetime license, or permanent free access unless Orbyt explicitly states that it does.

What we expect from testers

Beta participants should use the product normally and provide clear, constructive feedback when issues or opportunities are discovered.

Helpful feedback can include:

• Bugs or errors
• Features that do not work as expected
• Confusing screens or workflows
• Missing functionality
• Performance problems
• Compatibility issues
• Setup or installation problems
• Integration issues
• Suggestions for improvements
• Features you would like to see added
• General usability feedback

You do not need to be a professional software tester to participate.

Clear descriptions of what you were doing, what you expected to happen, and what actually happened are often extremely helpful.

Reporting bugs and feedback

Use your account's Development / Beta Program workspace to report bugs, submit suggestions, and respond to reviewers.

When possible, include:

• The product or feature you were using
• The steps that caused the issue
• What you expected to happen
• What actually happened
• Your device, browser, or operating system
• Screenshots where appropriate
• Any error message you received

Avoid submitting the same issue repeatedly unless you have new information to add.

For additional help, visit Orbyt Support.

Feedback visibility

Feedback may be visible to authorized Orbyt staff, product developers, reviewers, and other approved testers who have access to the same beta workspace.

This allows testers and developers to collaborate, confirm issues, discuss improvements, and avoid duplicate reports.

Do not include sensitive or confidential information in beta feedback.

Protect your information

Never submit:

• Passwords
• Authentication codes
• Private API keys
• Secret tokens
• Payment card information
• Customer passwords
• Private customer records
• Confidential business information that is not required for testing
• Personally sensitive information that is unrelated to the issue

If an issue appears to require sensitive information to reproduce, contact Orbyt Support rather than posting that information in a shared beta workspace.

Beta software can change

Development and beta products are still being tested.

Features may be:

• Added
• Removed
• Redesigned
• Renamed
• Temporarily unavailable
• Reset during testing
• Limited to certain users
• Changed before public release

A feature available during beta is not guaranteed to appear in the final released product.

Availability and reliability

Beta products may experience interruptions, bugs, incomplete features, reduced performance, or unexpected behavior.

You should not rely on a beta product as your only solution for critical business operations unless the beta documentation specifically states that it is suitable for production use.

Keep appropriate backups of important information when testing development software.

Data during beta testing

Some beta products may use temporary databases, test environments, development infrastructure, or experimental storage systems.

When this applies, the product page or testing instructions may explain whether data will carry over to the final released version.

Do not assume that beta data will automatically transfer to the production release.

Third-party services and integrations

Some beta products may connect to third-party services, APIs, payment providers, hosting services, or external platforms.

Those services may have their own terms, limitations, usage fees, or availability requirements.

Beta access to an Orbyt product does not automatically include paid access to third-party services.

Support during beta

Beta products may receive a different level of support than fully released products.

Support may be provided through:

• The Development / Beta Program workspace
• Product-specific feedback threads
• Orbyt support
• Developer communication
• Testing announcements
• Documentation supplied with the beta

Response times may vary depending on the product and stage of development.

Updates and testing requests

During a beta, Orbyt may ask participants to test a specific feature, retry a previously reported issue, review an updated workflow, or provide additional information.

You may also see announcements about new builds, known issues, maintenance, or upcoming changes within your beta workspace.

Leaving a beta

You may stop participating at any time unless a specific beta states otherwise.

If you no longer want access, contact Orbyt Support or use any available controls provided in your account.

Leaving a beta may remove access to beta-only products, features, data, or workspaces.

Removal from the program

Orbyt may remove or suspend beta access when necessary.

Examples may include:

• Misuse of beta systems
• Sharing access with unauthorized users
• Attempting to bypass access controls
• Abusive or disruptive behavior
• Security concerns
• Program closure
• Product cancellation
• Inactivity when active testing is required
• Violation of applicable Orbyt terms

Removing beta access does not affect unrelated products or services on your account unless a separate account issue exists.

Confidential or restricted betas

Most beta programs may be discussed normally unless the specific beta says otherwise.

Some development projects, however, may be marked confidential, private, invite-only, or subject to additional terms.

If a beta has special confidentiality requirements, you will be shown those requirements before or when access is granted.

No purchase required unless stated

Applying to a Development / Beta Program does not create a purchase, subscription, or paid commitment.

Some beta products may require an existing product, compatible service, third-party account, hardware device, or paid external service in order to function.

Any such requirement should be identified on the applicable product or beta listing.

What happens when testing ends

When a beta ends, the product may:

• Move to full release
• Continue into another testing phase
• Move to a paid plan
• Remain available to approved testers
• Be replaced by a newer version
• Be discontinued

If action is required from you, Orbyt will provide information through your account, the beta workspace, product page, or associated communication channels.

Beta participation does not guarantee release

Some products tested through the Development / Beta Program may never receive a public release.

Testing helps Orbyt determine whether a product is ready, useful, sustainable, and appropriate for the wider Orbyt ecosystem.

Your feedback matters

The purpose of the Development / Beta Program is not only to find bugs.

Your experience can influence how products are designed, which features are prioritized, how workflows are simplified, and what ultimately becomes part of the Orbyt ecosystem.

If you are interested in helping us build what comes next, look for products marked Development / Beta and submit an application from the product listing.

Build early. Test honestly. Help shape what launches next.