Introducing FlaskTrack: Why We Built a Modern Laboratory Operating Platform

Scientific organizations are expected to move quickly while preserving accuracy, repeatability, traceability, and institutional knowledge. A biotechnology startup may begin with a few researchers, a shared spreadsheet, a folder of protocols, and an inventory list. A tissue culture facility may rely on handwritten transfer logs, media preparation sheets, and labels. A research laboratory may use a different tool for notes, samples, sequences, files, schedules, and reports.

These approaches are understandable. They are inexpensive, familiar, and flexible. The problem appears later, when the organization grows and the cost of fragmented information begins to exceed the convenience of the original tools.

FlaskTrack is our response to that problem. It is a modern laboratory operating platform developed by Santurce Software to connect procedures, samples, batches, materials, inventory, users, molecular records, files, approvals, reports, and compliance evidence in one system.

The Spreadsheet Stage

Nearly every organization passes through a spreadsheet stage. Spreadsheets are effective for early lists, calculations, small inventories, simple schedules, and lightweight reporting. They allow a team to begin working without a major implementation effort.

The same flexibility that makes spreadsheets useful also makes them difficult to control. A spreadsheet does not inherently understand that a sample came from another sample, that a batch followed a particular version of a protocol, that an ingredient lot was consumed during a specific step, or that an approval must be linked to a named user and an exact record state.

As the organization grows, teams often create more files rather than a better system. A master inventory sheet becomes several inventory sheets. Protocols are copied into new folders. Batch records are exported into PDFs. Supporting evidence is attached to email. Schedule changes live in chat messages. Reports are assembled manually at the end of the month or in preparation for an audit.

The Real Cost of Disconnected Laboratory Tools

The cost of fragmented software is not limited to software subscriptions. It appears in repeated data entry, inconsistent naming, missing context, delayed decisions, avoidable inventory shortages, difficult onboarding, and time spent reconstructing what happened.

A laboratory record is most useful when its context is preserved. A sample should remain connected to its source, species, protocol executions, files, observations, transfers, and resulting batches. A batch should remain connected to its workflow, materials, users, step records, deviations, approvals, release decision, and reports. An inventory transaction should explain not only that quantity changed, but why it changed and which operation caused it.

When those relationships are distributed across several tools, the organization must recreate them manually. That reconstruction is slow during normal operations and particularly expensive during investigations, technology transfer, customer diligence, quality review, or regulatory inspection.

Why Existing Laboratory Systems Often Fall Short

The laboratory software market includes many capable products, but smaller and growing organizations frequently encounter a difficult choice. Generic project-management or database tools are approachable but lack scientific and compliance context. Traditional enterprise laboratory systems may provide extensive capabilities but require costly implementation, consulting, configuration, validation, and ongoing administration.

In practice, this leaves many teams in the middle. They need more structure than spreadsheets can provide, but they are not ready to adopt a large enterprise platform. They need traceability without excessive overhead, controlled workflows without a rigid user experience, and serious engineering without a multi-year transformation project.

We built FlaskTrack for that middle ground and for the organizations that expect to grow beyond it.

Execution, Not Just Documentation

A central design principle in FlaskTrack is that procedures should do more than exist as uploaded documents. A procedure should be capable of guiding actual work.

FlaskTrack protocols are structured and versioned. They can define steps, timing, required materials, tools, biological entities, inventory effects, data collection requirements, and execution instructions. Protocols can be assembled into reusable workflows and scheduled against samples or batches.

During execution, the system can create step-level records, show required resources, capture observations, preserve files, record completion, update status, and associate the work with the responsible user. This creates an operational record as the work happens rather than forcing the team to reconstruct it afterward.

Samples and Batches Need Context

Sample tracking is often described as maintaining an identifier and a status. In real laboratories, samples exist within a network of relationships. They may be derived from another sample, associated with a species, transformed with a plasmid, processed through a workflow, combined into a batch, stored at a location, transferred, archived, or linked to multiple files and observations.

Batches are similarly contextual. A batch is not only a row in a table. It represents a controlled execution of a process using particular materials, procedures, equipment, users, dates, decisions, and resulting evidence.

FlaskTrack is designed to preserve these relationships so that users can move from the high-level record to the underlying execution history without switching systems or manually joining data.

Inventory Should Participate in Laboratory Work

Inventory systems are frequently separated from execution systems. This creates a gap between what the laboratory plans to do and what materials are actually available.

FlaskTrack treats inventory as part of the laboratory workflow. Ingredients, tools, biological materials, suppliers, supplier items, lots, locations, stock, reservations, consumption, purchase orders, receiving, and adjustments can be linked to the operations that need them.

The goal is not simply to display an on-hand quantity. The goal is to help the laboratory understand whether planned work is ready, where shortages exist, what must be procured, and how inventory changed during execution.

Molecular Biology Belongs in the Operational Record

Molecular biology teams commonly use specialized sequence tools while tracking project context, approvals, experimental execution, and resulting samples somewhere else. FlaskTrack includes molecular design capabilities so plasmids, sequence versions, features, primers, primer pairs, assembly designs, and analyses can remain connected to the broader laboratory record.

Sequence records can be versioned, reviewed, approved, and published. Molecular designs can be associated with projects and catalog records. Primers and assemblies can be verified. This provides a path from design intent to controlled execution and later traceability.

Compliance Should Be Part of Normal Work

Compliance becomes expensive when it is treated as a separate activity performed after operational work is complete. Teams then spend time collecting screenshots, locating files, confirming who approved a record, reconciling dates, and explaining why information differs between systems.

FlaskTrack is designed around the idea that auditability should emerge from ordinary use. Record creation, updates, approvals, signatures, execution, release, publication, archival, and exports can generate structured history tied to named users and specific entities.

The platform includes role-based authorization, audit trails, electronic signatures, controlled versioning, review and approval workflows, compliance checklists, evidence files, validation documentation, and security controls. These features are intended to support organizations operating under applicable GxP requirements and FDA 21 CFR Part 11.

Validation Documentation as a Product Capability

Computer system validation is frequently reduced to a folder of documents created late in an implementation. We believe validation support should be maintained alongside the product lifecycle.

FlaskTrack includes a validation package designed to help customers evaluate and validate the system for their intended use. The package can include user requirements, functional specifications, design specifications, risk assessment, traceability, installation qualification, operational qualification, performance qualification, validation protocols, validation reports, release evidence, Part 11 control mappings, configuration baselines, periodic review resources, migration protocols, retirement planning, supplier qualification, and disaster recovery evidence.

This documentation does not replace customer validation. It gives customers a stronger starting point and a more transparent view of the product controls and release evidence available to support their validation process.

Why We Chose a Modern Engineering Stack

Laboratory systems hold operationally important data and often remain in use for many years. Their architecture must support correctness, security, performance, maintainability, and controlled evolution.

FlaskTrack is built in Rust, a modern systems programming language recognized across industry and government for its emphasis on memory safety, reliability, and performance. Rust has been adopted for security- critical software and is recommended by U.S. cybersecurity agencies as part of broader efforts to reduce memory safety vulnerabilities in modern software systems.

Combined with PostgreSQL, FlaskTrack emphasizes strongly typed domain models, transactional consistency, server-side validation, structured authorization, comprehensive automated testing, and explicit relationships between laboratory records. These engineering practices help produce software that is dependable, maintainable, and suitable for organizations operating under quality and regulatory requirements.

API-Ready by Design

Laboratories should not be trapped inside a single application. Operational data may need to flow into analytics, finance, customer portals, automation systems, instruments, internal applications, or data warehouses.

FlaskTrack is designed with structured APIs and exports so organizations can integrate laboratory records with the rest of their technology environment. An API-first mindset also improves the internal consistency of the application because the same domain concepts must be represented clearly and predictably.

Artificial Intelligence as a Laboratory Assistant

Artificial intelligence is becoming an increasingly valuable tool for scientific organizations, but we believe its greatest value comes from accelerating laboratory work—not replacing scientific judgment. FlaskTrack integrates AI throughout the platform to reduce repetitive administrative work while keeping researchers, laboratory managers, and quality teams in control of every important decision.

Laboratories spend countless hours converting published methods, standard operating procedures, and internal documentation into executable laboratory workflows. FlaskTrack can use AI to help transform research papers, PDF documents, Word files, and plain-language descriptions into structured protocols, reusable workflows, and standardized laboratory procedures. Scientists review every generated protocol before it becomes part of a controlled process, allowing AI to accelerate authoring while preserving scientific oversight.

The platform also applies AI within FlaskTrack's molecular biology workspace. Researchers can describe a cloning objective, experimental design, or construct requirements using natural language and receive assistance generating plasmid designs, annotating sequence features, organizing assemblies, suggesting primer strategies, documenting design intent, and scaffolding molecular biology projects. These capabilities help reduce documentation effort while maintaining complete version history and traceability throughout the design lifecycle.

Operational reporting is another area where artificial intelligence can eliminate manual work. Rather than exporting data into spreadsheets and manually constructing reports, users can describe the information they need using natural language. FlaskTrack can assist in generating SQL queries, analytical reports, dashboards, regulatory summaries, customer deliverables, and structured data exports that are based on the laboratory's operational records. Generated queries can be reviewed by technical users before execution, providing both flexibility and transparency.

Beyond authoring and reporting, AI can help summarize laboratory activity, identify operational trends, explain deviations, draft investigation notes, assist with compliance documentation, and answer questions across connected laboratory records. Because FlaskTrack understands the relationships between protocols, workflows, samples, batches, inventory, molecular designs, approvals, and audit history, AI responses can be grounded in structured operational data instead of isolated documents.

Our objective is not to replace laboratory expertise. It is to eliminate repetitive administrative effort so scientists, engineers, and quality professionals can spend more time designing experiments, interpreting results, improving processes, and advancing research while maintaining complete traceability and organizational control.

FlaskTrack does not use customer laboratory data to train public artificial intelligence models or commercial foundation models. Customer data remains under the customer's control.

Designed for Teams That Are Still Growing

A startup laboratory should not need to predict its complete operating model before adopting structured software. At the same time, the system should not become unusable when the team adds new users, new facilities, new processes, new products, or new compliance requirements.

FlaskTrack is being designed to support progressive maturity. A research team can begin with protocols, samples, inventory, and notes. A production team can add batches, procurement, review, release, and reporting. A regulated organization can implement signatures, audit review, validation, controlled approvals, policies, and periodic oversight.

Who FlaskTrack Is For

FlaskTrack is intended for scientific organizations that need more than a generic database but want a more modern, practical path than a traditional enterprise implementation.

• Biotechnology startups establishing repeatable operations
• Research laboratories standardizing protocols and records
• Tissue culture facilities managing media, transfers, lineage, and contamination
• Synthetic biology teams connecting molecular designs with laboratory execution
• Mycology laboratories tracking cultures, materials, batches, and observations
• Academic laboratories improving continuity and reproducibility
• Manufacturing organizations requiring traceability and controlled execution
• Quality-focused teams preparing for customer, partner, or regulatory scrutiny

What Makes FlaskTrack Different

We do not view FlaskTrack as a collection of unrelated modules. Its value comes from the relationships between them. A protocol can define materials. A workflow can schedule that protocol. A sample or batch can execute the workflow. Inventory can be checked and consumed during execution. Files and observations can be attached in context. Audit records can preserve significant actions. Reports can be generated from the resulting operational history.

This connected model is what allows the platform to become an operating system for laboratory work rather than another place where data must be copied.

What We Have Learned Building FlaskTrack

Building laboratory software requires more than creating forms and database tables. Scientific records have lifecycles. They are drafted, reviewed, approved, executed, revised, released, superseded, archived, and sometimes invalidated. Their meaning depends on relationships, timing, identity, and context.

We have also learned that usability and compliance cannot be treated as opposing goals. A system that users avoid will produce incomplete records. A system with no controls will produce unreliable records. Good laboratory software must make the correct action understandable and the resulting evidence automatic wherever possible.

The product continues to evolve through implementation work, automated testing, domain research, direct user feedback, and the practical challenges of connecting real laboratory workflows.

The Road Ahead

FlaskTrack is already a broad platform, but the roadmap remains focused on deepening the connection between planning, execution, quality, and evidence. Areas of continued development include more executable validation workflows, expanded instrument and system integrations, stronger analytics, improved inventory forecasting, richer molecular design tools, enhanced reporting, and additional customer configuration controls.

We are also continuing to improve the product experience for different laboratory domains so teams can use terminology, workflows, and views that fit their work without losing the benefits of a shared operational model.

A Product and an Engineering Case Study

FlaskTrack is a commercial product, but it also demonstrates the type of engineering Santurce Software delivers. It combines domain modeling, database design, secure application architecture, workflow automation, cloud infrastructure, compliance controls, technical documentation, testing, and product design in one long-term software system.

The same approach applies beyond laboratories. Complex businesses often rely on fragmented tools because their workflows do not fit generic software. Our work is to understand those workflows, model them clearly, and build dependable systems that make operations easier to run and easier to understand.

Conclusion

Laboratories should not have to choose between flexible but uncontrolled spreadsheets and expensive, difficult-to-use enterprise systems. They should be able to adopt structured software that fits current operations, supports future growth, and preserves the context needed for reliable science and controlled production.

That is why we built FlaskTrack: to give scientific organizations one connected place to define work, execute it, understand it, and preserve the evidence it creates.