web-vs-package-jp

GGGenome: web edition and package edition compared
Contents
- Web edition / package edition in detail
- Use and environment
- Search performance and limits
- Analysis support
- Databases
- What the package edition adds
- Search unpublished sequences without sending them out
- Run large-scale searches
- Analyze large result sets efficiently
- Spot key off-target candidates quickly
- Add your own databases as search targets
- Which edition should you choose?
- Frequently asked questions
Web edition / package edition in detail
Last updated: August 2026
Specifications are as of August 2026. Search limits, timeouts and system requirements are subject to change.
Use and environment
Item | Web edition | Package edition |
|---|---|---|
Delivery | Used from a browser (published by DBCLS) | Supplied on SSD; runs offline |
Confidentiality of the query sequence | The query sequence is sent to the server | Not sent externally. Sequences are not saved to the SSD and are deleted when the system stops |
System requirements | A browser | 64-bit Windows 11 Pro version 21H2 or later / Windows 10 Pro 21H1 or later. Docker Desktop, Hyper-V enabled, 8 GB RAM or more |
Licensing | — | Perpetual plan (unrestricted license, one year of support) or subscription plan (license, support and updates for the contract period) |
Search performance and limits
Item | Web edition | Package edition |
|---|---|---|
Minimum query length | 6 bases | 6 bases |
Maximum tolerance | Up to 25% of query length | No limit |
Results shown per HTML page | 50 | 50 |
Results returnable via API | 100,000 | 10,000,000 |
Internal hit limit | 100,000,000 | 1,000,000,000 |
Search timeout | 30 seconds | 86,400 seconds (24 hours) |
Analysis support
Item | Web edition | Package edition |
|---|---|---|
Bioretool search support script | — | Batch search across multiple queries, search across multiple databases, merging of pre- and post-splicing results, execution history, summary export |
Gene-of-interest highlighting | — | Supplying a list of genes of interest enables highlighting, filtering and CSV export of results |
Databases
Item | Web edition | Package edition |
|---|---|---|
Databases searched | Databases published by DBCLS | Drug discovery basic pack (9 species; genome / mRNA / pre-mRNA) |
Adding databases | — | Optional DBs (every database searchable in the GGGenome web edition) and custom DBs (your own sequences and other published data) can be added. Additional fees apply |
What the package edition adds
Search unpublished sequences without sending them out
The package edition runs from an SSD and searches offline. Query sequences are held temporarily on the system, are not saved to the SSD, and are deleted when the system stops. Sequences under development never need to leave your organization.
Run large-scale searches
The web edition applies search limits to manage server load. The package edition relaxes those limits, which suits analysis pipelines that process many candidate sequences in one run.
Item | Web edition | Package edition |
|---|---|---|
Maximum tolerance | Up to 25% of query length | No limit |
Results returnable via API | 100,000 | 10,000,000 |
Internal hit limit | 100,000,000 | 1,000,000,000 |
Search timeout | 30 seconds | 86,400 seconds (24 hours) |
The minimum query length (6 bases) and the number of results shown per HTML page (50) are the same in both editions.
Analyze large result sets efficiently
The package edition includes Bioretool, a search support script that runs batch search operations from a UI.
Batch search across multiple queries
Search across multiple databases
Merge pre- and post-splicing results
Manage execution history
Export a summary of results
Spot key off-target candidates quickly
Supplying a list of genes of interest enables highlighting, filtering and CSV export of matching results, so the relevant hits can be pulled out of a large result set.
Add your own databases as search targets
Optional DBs cover every database searchable in the GGGenome web edition. Custom DBs let you add your own nucleotide sequences or information published elsewhere. Additional fees apply in both cases.
Which edition should you choose?
■ Try the web edition published by DBCLS
Frequently asked questions
Q. What is the difference between the GGGenome web edition and package edition?
A. The main differences are whether query sequences leave your organization, the search limits, the analysis support features, and support for your own databases.
The web edition is published by DBCLS and used from a browser. The package edition runs in your local environment, with relaxed search limits, analysis support features, and the option to add your own databases. Because the search engine and databases are packaged as a consistent set, the same query returns the same results in either edition.
Q. Which edition suits searching unpublished sequences?
A. The package edition.
It runs from an SSD and searches offline, so sequences under development never need to be sent outside your organization. For straightforward searches of published sequences, the web edition is sufficient.
Q. Does the GGGenome package edition send query sequences to an external server?
A. No.
The package edition runs offline. Query sequences are held temporarily on the system, are not saved to the SSD, and are deleted when the system stops.
Q. Can I search my own sequence databases?
A. Yes, in the package edition.
Custom DBs let you add your own nucleotide sequences or information published elsewhere. Optional DBs cover every database searchable in the GGGenome web edition. Additional fees apply in both cases.
Q. How can I try GGGenome first?
A. Use the web edition published by DBCLS.
Because the Database Center for Life Science (DBCLS) publishes it, you can check the interface and search results directly. Contact us about evaluating the package edition or requesting a quote.
Back to top page
chevron_right