
Engine
Sequence annotation
Raw sequence in, described sequence out. Features marked, reading frames found, translations laid against the strand, and a map you can zoom into rather than squint at.
Biopython
annotation engine
seqviz
interactive viewer
GenBank
and FASTA export
Free
CPU engine
01
What the engine does
A sequence file on its own tells you almost nothing. It is a long string with no landmarks, and the work of finding the landmarks โ where the coding region starts, which frame it reads in, where the promoter sits, whether that stop codon is real or an artefact of the frame you happened to pick โ is the work everyone does first and nobody enjoys doing twice.
The annotation engine does that pass for you. Built on Biopython, it parses what you give it, marks the features it can identify, scans every frame on both strands for open reading frames, and produces translations alongside the nucleotide view. The result is rendered as an interactive map through seqviz, linear or circular, zoomable from whole-plasmid down to the individual base.
It is the entry point to most of the platform. Sequences arrive here before they go anywhere else, because everything downstream โ assembly, primer design, codon adaptation โ works better against something that has already been described.
02
What you supply
Upload a GenBank or FASTA file, paste a sequence directly, or pick one that is already in the system: a gene from any of the 65 organisms in the catalog, a construct from a project, or a record carried over from an earlier run. Catalog entries are addressable by their ID, so pulling the sequence behind SS-0421 is a lookup rather than a download-and-reupload round trip.
Existing annotation is respected. If your GenBank file already carries features, they come through intact and the engine adds to them rather than overwriting โ a distinction that matters when the file has been curated by hand and you would rather not lose that work.
03
What the screen shows back
Zoomable map
seqviz renders the sequence as an interactive map. Switch between linear and circular, zoom from whole-record overview down to single bases, and click any feature to see its coordinates, strand and type.
Feature track
Coding sequences, regulatory elements, tags and markers are drawn on the strand they belong to, with overlaps shown as overlaps rather than flattened into a single row.
Open reading frames
All six frames are scanned and the candidate ORFs listed with their start positions, lengths and frames. Short spurious hits can be filtered out by length so the real candidates are not buried.
Translations
Protein translations sit under the nucleotide view, frame by frame, so a frameshift is something you see immediately instead of discovering three steps later.
Search and jump
Jump to a coordinate, a feature name or a motif. Useful when you know roughly where the thing you care about is but not exactly.
Composition summary
Length, GC content and a per-feature breakdown, shown as a panel beside the map rather than as a separate report you have to go and find.
04
Run profile
- Engine
- Biopython
- Viewer
- seqviz, linear and circular
- Accepts
- GenBank, FASTA, pasted sequence, catalog ID
- Exports
- GenBank, FASTA
- Engine class
- CPU
- Credit cost
- Free
- Typical runtime
- Seconds for a gene, under a minute for a plasmid
Annotation is a CPU engine, which on this platform means it costs nothing to run. There is no quota to watch and no reason to batch your work to save credits โ annotate the same sequence six times with different filter settings if that is what it takes. Credits exist only for GPU engines, where $25 buys 250 credits and one credit covers roughly one Standard job.
Exports are GenBank and FASTA. GenBank carries the annotation with it, which is the point: the file you download opens in whatever desktop tool your collaborator prefers and still knows where its features are. FASTA is there for the cases where you just need the sequence and nothing else.
05
Who uses it
Researchers use it as a first look โ a sequence arrives from a collaborator or a sequencing run and needs to be understood before anything is decided about it. Educators use the map as a teaching surface, because a zoomable rendering of a real construct explains reading frames faster than a diagram does. Developers pull the same annotation through the API and never open the viewer at all.
Inside the catalog, it is simply infrastructure. Every one of the 1,000 constructs and all 14.1 Mbp of designed DNA has been through this engine, which is why the records behind the heat ladder โ from 100 SHU at the gentle end to 16,000,000 SHU at the top โ read as annotated designs rather than as anonymous strings.
Ready to run it
Try this in the Splice Platform.
CPU engines are free to run. GPU engines run on prepaid credits.
Related