Sequences

Find the patents that hold your sequence

Search the DNA and protein sequences in patents for prior art and freedom to operate, check sequence listings before you file, and keep a record of every search.

A new account gets a free 30-day trial.

Before you sign in

  • Methods

    Which search method fits your query and why, with recorded runs.

  • Data

    What each data source holds, with its count and date on this server, how often it updates and its license.

  • Benchmarks

    Each recorded run of the search methods, with its data, its result and its evidence record.

  • Examples

    Working examples, open without signing in.

What Sequences does

Made for patent sequence work

  • Prior art: find what was published before a date, one row for each patent family, with each match's alignment.
  • Freedom to operate: see which patents hold your sequence or a close match, and who filed them.
  • Sequence listings: check a WIPO ST.26 listing before you file it, and search its sequences.

What it searches

Patent DNA and Patent proteins hold the sequences of patent publications, US published applications since 2001 among them, and each week's applications and grants arrive as an addition. Beside them are Swiss-Prot, TrEMBL, ESTs and NCBI core_nt. Data sources gives each one's count, date and license.

Plans and prices

Prices are in US dollars. The hosted service starts with a free 30-day trial, and the server edition with a free 90-day evaluation.

  • Hosted service

    $99 per user per month

    or $990 per user per year

    Search on ConductScience servers, with nothing to install.

  • Server edition

    $12,000 per server per year

    Run Sequences in your own cloud or data center.

  • Enterprise

    From $350,000 per year for up to 250 named users

    For agencies and large organizations, in your own cloud.

  • Deployment

    From $150,000 per project, each quoted at a fixed price

    A fixed price for setting up Sequences in your cloud.

Security, accessibility and programs

  • Security

    How to report a vulnerability, who can see your work, the audit log and what each release records.

  • Accessibility

    What the accessibility tests check, what they do not check yet, and how to report a problem.

  • API reference

    Every route a program uses, with its parameters and answers, and how to sign in with a token.

  • Your own server

    Run the same release in one container on your own Linux server, with your own sign-in.