From time to time, Pergamon introduces new features labelled Beta. If you have seen this label and wondered what it means for you as a user, this article explains it in plain terms — what Beta is, what to expect from it, and how to make the most of it.
What Beta means at Pergamon
When Pergamon labels a feature Beta, it means the feature is real, functional, and available for use but it has not completed the full development and quality cycle that a generally available feature has. It is an early version, released deliberately to a selected group of users so that real-world usage can inform and accelerate its development.
Beta is a stage in a feature's lifecycle, not a measure of its ambition or importance. Some of Pergamon's most significant capabilities have launched as Beta features. The label signals where a feature is in its journey, not whether it is worth using.
Info
Different software vendors use different labels for pre-release features. You may have encountered terms such as Technical Preview, Early Access, or Preview in other products you use. While the specific label varies, the underlying principle is the same — a feature is made available to select users ahead of its general release, with the understanding that it is still evolving. At Pergamon, we use Beta to communicate this stage.
Beta at Pergamon works the same way. A Beta feature is:
- Real and usable — it is not a demo or a mock-up. You can use it to do real work.
- Early in its development — the core functionality is in place, but it has not gone through the full development and testing process that a finished feature would.
- Actively being worked on — the Pergamon team is continuing to build, refine, and improve it based on how real users interact with it.
- Not the final version — what you see today is a starting point, not the finished product. It will look and behave differently as it matures.
Info
Beta features in Pergamon are made available to a selected group of customers before a wider release across other Pergamon tenants or subdomains. Being invited to use a Beta feature means you are among the first to experience it and your feedback directly shapes how it develops.
What the Beta label looks like in Pergamon
In Pergamon, the Beta label appears directly in the feature interface. Here are two examples from the current 3.9.0 release:
Pergami AI
The Beta label displayed in the Pergami AI panel header alongside the online status indicator.
Asset Annotation Editor
The Beta banner displayed at the top of the Asset Annotation Editor properties panel, indicating the feature is not intended for production use in its current state.
Info
Whenever you see the Beta label in Pergamon, there may be a link to the feature's dedicated help article explaining its its current scope, known limitations, and what to expect. Look for the Learn more link in the Beta banner or search the Pergamon Support Portal.
What to expect from a Beta feature
When you use a Beta feature in Pergamon, set your expectations accordingly. Here is what is normal and expected during a Beta phase:
| You might notice | Why this happens |
|---|---|
| Some things do not work exactly as you expect | The feature is still being refined. Rough edges are a normal part of early access. |
| A tool or option you need is not there yet | Beta features launch with core functionality. Additional capabilities are added progressively. |
| The feature behaves differently from one update to the next | Active development means the feature is continuously updated. Changes are improvements, not instability. |
| It does not do everything a similar tool you have used before does | Beta features are scoped for the workflows Pergamon users need most. The feature set grows over time. |
| The visual design or layout feels slightly unpolished | UI polish is typically one of the last stages of development. It improves significantly before general release. |
Tip
If something is not working the way you expect, check whether the behavior is listed as a known Beta limitation in the feature's documentation before submitting a support request. Many Beta behaviors are already known and being addressed.
What Beta does not mean
Beta is sometimes misunderstood. Here is what the Beta label does not mean at Pergamon:
- It does not mean the feature is broken. Beta features work. They are simply earlier in their development cycle than a fully released feature.
- It does not mean your work will be lost. Content you create or save using a Beta feature is stored normally. Beta refers to the feature's maturity, not its reliability in saving your work.
- It does not mean Pergamon has not tested it. Beta features go through internal testing before release. Beta simply means that real-world usage reveals things that internal testing cannot.
- It does not mean it will always be this way. Beta is a phase, not a permanent state. Every Beta feature at Pergamon is on a path to a full, polished release.
Beta features and support coverage
Because Beta features are still in active development, they are handled differently from fully released features when it comes to support.
Warning
Beta features are not covered under Pergamon's standard Service Level Agreement (SLA). This means that response and resolution times for issues related to Beta features may differ from those that apply to fully released features. Issue reports submitted for Beta features are reviewed and triaged through our Beta feedback process rather than standard support channels.
This does not mean your feedback goes unheard, quite the opposite. Reports submitted during a Beta phase are reviewed directly by the product team and carry significant weight in shaping the feature's development. However, they are treated as product feedback rather than support incidents with guaranteed resolution timelines.
If you are unsure whether an issue you are experiencing relates to a Beta feature or a fully released part of Pergamon, contact the support team and they will advise on the appropriate process.
How to use Beta features effectively
- Read the feature documentation first. Each Beta feature has a dedicated help article explaining what it can do, what its current limitations are, and any known behaviors to be aware of.
- Start with lower-stakes work. If you are trying a Beta feature for the first time, use it on a document or asset that is not time-critical while you get familiar with how it behaves.
- Do not rely on it for urgent production deadlines. Beta features are not recommended as the primary tool for work with a fixed, immovable deadline until you are confident in how the feature performs for your specific workflow.
- Save your work regularly. As with any early-stage feature, saving frequently is good practice.
- Check for updates. Beta features are updated frequently. An issue you encountered last week may already be resolved in the latest version.
How your feedback shapes what comes next
The single most valuable thing you can do during a Beta phase is share what you experience. Not just what does not work but what you wish it could do, what feels awkward, and what works better than you expected.
Every Beta feature in Pergamon has a feedback channel. Use it. The product team reads every submission and your usage patterns, pain points, and feature requests directly influence what gets prioritized in the next release cycle.
Beta is also when Pergamon moves fastest. Enhancements and fixes are delivered at an accelerated pace during this phase specifically to resolve issues, close gaps, and progress the feature toward its full release. Completing the Beta phase and reaching general availability is the goal. Your feedback is what gets it there.
Note
All feedback submitted during Beta is reviewed and analysed by the product team. Not every request will be implemented — submissions are evaluated against user needs, technical feasibility, and product priorities to identify the strongest candidates for development. If your feedback is not reflected in an upcoming release, it does not mean it was not considered.
Beta access at Pergamon is not just early access to a feature, it is an invitation to help build it.
Info
For questions about a specific Beta feature, refer to that feature's dedicated help article. For general questions about your Pergamon subscription or account, reach out to the support team through the Pergamon Support Portal.
Comments
0 comments