Plasmid library setup
Historical GenBank, FASTA and SnapGene files import as plasmid records with topology and annotations; host, storage location and identifier fields follow current organizational rules.
Plasmid and vector management
Plasmid libraries, constructs and mutagenesis, held in auditable R&D records
For protein drug development and CDMO teams. GenBank and SnapGene files scattered across personal computers become structured records, each sequence tied to an organizational identifier, encoded protein and batches.
Book a demoUse cases
From plasmid records to construct changes
Duplicate construct checks
The same plasmid is often saved from different start positions across team members' files. With a unique sequence field, rotated and reverse-complement copies count as the same sequence at entry.
Site-directed mutagenesis approval
Construct changes go to approval with the changed position, before and after bases and sequence hashes shown; annotation-only edits state that residues are unchanged.
From plasmid to protein and batch
Relations link plasmids to encoded proteins and production batches, so change assessment can review batches that use the same vector.
Screens show demonstration data: sequences from public NCBI and UniProt records, fictional names.
Configuration demo