c.125A>G
Clone B4 · 1,371 A>G on pCV-EGFP
- Effect
- Missense in EGFP · p.Lys42Arg (AAG → AGG)
- Evidence
- fwd Q40 · rev Q38 · reads agree · no secondary peak
- Rule
- ROI_DAMAGING A protein-changing edit in a region of interest fails the clone.
In development · early access open
Every clone, verified in a minute.
Drop in your plasmid maps and sequencing results. clone-verify checks each clone against the construct you designed and gives it a verdict, with the evidence beside every call.
Runs on your computer. Your sequences never leave it.
Plate 07 · 93 clones · example
Reads GenBankSnapGene .dnaFASTA
·
Sanger .ab1Whole-plasmid consensus
How it works
From a plate of results to decisions, in three steps.
Checking a single Sanger trace by hand takes an experienced researcher about five minutes. A 96-well plate is an afternoon. clone-verify does the checking and shows you only what needs your judgment.
01
Drop your files
Your references as GenBank, SnapGene or FASTA. Your results as Sanger traces or whole-plasmid consensus from your sequencing provider. A whole plate at once.
02
Every clone is checked
Each result is aligned to its circular reference, every difference is called, and its effect on your features is worked out: a silent change in the backbone, or a frameshift in your insert.
03
Decide with the evidence
Pass, Fail or Review for every clone, with the trace, the quality and the rule that decided. Triage from the keyboard and export a report anyone in the lab can read.
What you'll see
The plate first. The evidence one click away.
Plate 07
Design preview with example data. The app is in development.
Why clone-verify
Built for the question you actually have: is this clone right?
Verdicts, not just alignments
Every clone gets Pass, Fail or Review, so you see at a glance which ones need you.
Knows what a change does
Silent, missense, nonsense or frameshift, worked out on your annotated features and regions of interest.
Sanger and whole-plasmid together
Forward and reverse reads merged per clone, and whole-plasmid consensus checked end to end, in one report.
Your sequences stay yours
Runs in your browser or on your desktop and works offline. Nothing is uploaded.
Rules you can read
Every verdict names the rule that decided it, with the trace and quality behind it. No black box.
Fast, from the keyboard
Move between clones with J and K, accept with A, flag with F. A plate reviewed in minutes.
Drawn from the data
The signal is the light.
Wells, traces and maps carry their meaning in color: verdicts glow, bases keep the sequencer's colors, and everything else steps back.
Early access
Join the early access list.
Beta invites go out in waves, starting with labs that verify clones every week: academic groups, biotech teams, core facilities and iGEM teams.
- Beta invites first. Use clone-verify on your own plates before public launch.
- Early-adopter pricing. First access to launch licenses, before anyone else.
- Shape what gets built. Tell us your file formats and workflow, and we build for them.
Questions
Good to know
Which files does clone-verify read?
References as GenBank (.gb, .gbk), SnapGene (.dna) or FASTA. Results as Sanger traces (.ab1) or whole-plasmid consensus sequences (FASTA) from long-read sequencing services.
Are my sequences uploaded anywhere?
No. clone-verify runs on your computer, in the browser or as a desktop app. Your sequences never leave it, which also makes it a good fit for labs that keep constructs confidential.
When can I use it?
The verification engine is being built now. Beta invites go out in waves, and people on the early access list get them first.
What will it cost?
Pricing isn't final. There will be academic and commercial licenses, and early access members hear about them first.
Is it for clinical or diagnostic use?
No. clone-verify is a research tool for molecular biology and is not intended for clinical or diagnostic use.