LABMAS

What the company appears to be: LABMAS is a self-reported, single-developer project that claims to be an application for managing mouse colonies in research labs. The author states it supports digital cage cards, breeding planning, animal tracking, IACUC record keeping, and role-based training within one auditable lab workspace.

What changed: During the OpenAI 2026 hackathon (Build Week), the author claims to have added "practical breeding decision support", "safer lab administration", "future-facing IACUC tracking", and "training for different user roles". The project was reportedly already functional before this period, with the author stating they documented what was pre-existing versus what was added during the competition.

The single most important open question: Is LABMAS a working application that researchers actually use, or is it a prototype or demonstration tool? The description states no revenue, customers, or traction data are available beyond self-reporting. There is no evidence of adoption, usage metrics, or institutional deployment.

The description states that LABMAS is a Flask-based web application built with Python, Jinja, Bootstrap, SQLAlchemy, Alembic, PostgreSQL, and SQLite. It uses Codex (GPT 5.5 and 5.6) for development assistance. The system supports:

• Digital cage cards and barcodes
• Animal tracking (transfers, breeding setups, litters, weaning, treatments, euthanasia)
• Searchable live cohorts by genotype, strain, sex, age, cage type, and reproductive readiness
• Breeding planning from experimental targets to estimate demand, breeder cages, source cohorts, shortages, and dates
• Task assignment with Outlook-compatible reminders
• Reports on animal usage and estimated per diem (with Excel export)
• Lab and user administration, protocols, rooms, genetic profiles
• IACUC tracking for approval dates and genotype-level allocations
• Role-based training within the application

The author notes that LABMAS does not automatically move animals or enforce regulatory limits; it is designed to support decision-making without making decisions.

Evidence: Self-reported by the author. No independent verification of functionality, performance, or actual use.

The author positions LABMAS as a centralized, auditable workspace for managing mouse colonies in research labs. It is described as a tool that brings together tasks like breeding planning, cage tracking, and IACUC compliance into one application.

The claim evolution shows:

• Initial problem: Disorganized colony data across spreadsheets, emails, and people’s memories.
• Solution: A digital platform to centralize and streamline lab operations.
• Evolution during Build Week: Addition of breeding decision support, safer administration, IACUC tracking, and role-based training.

The author states that LABMAS grew from personal experience into a working production application. It is described as essential for daily research activities in their own lab and colleagues’ labs.

Evidence: Self-reported claims about positioning and evolution. No evidence of prior deployment or user feedback beyond the author’s account.

The description states that LABMAS is intended for researchers working with mouse colonies, particularly immunologists. It supports tasks like breeding planning, animal tracking, and IACUC compliance in research labs.

The target customer appears to be:

• Research labs managing mouse colonies
• Immunologists or other scientists who work with genetically modified mice
• Labs seeking centralized digital tools for colony management

No specific customer segments, institutional types (e.g., universities, pharma), or user roles beyond "researchers" are detailed. The author mentions “role-based training” but does not specify what those roles are.

Evidence: Self-reported positioning and target audience. No evidence of actual customers, institutional adoption, or segmentation data.

The description does not state any pricing model, licensing terms, or revenue streams. It is unclear whether LABMAS is offered as a SaaS product, open-source tool, or internal lab solution.

There is no mention of:

• Subscription fees
• One-time purchases
• Freemium models
• Institutional licensing
• Integration with billing systems

The author mentions future plans to integrate with Laboratory Animal Resources Center (LARC) operations and support warnings and reviews, but these are speculative.

Evidence: Not evidenced. No business model or pricing information provided.

LABMAS is built using:

• Framework: Flask
• Language: Python
• Templates: Jinja
• UI: Bootstrap
• Database: PostgreSQL, SQLite
• ORM: SQLAlchemy
• Migration tool: Alembic
• Deployment: Docker, gunicorn, fly.io
• AI assistance: Codex (GPT 5.5 and 5.6)

The author states that GPT was used for:

• Database models
• Workflows
• Interfaces
• Tests
• Browser validation
• Deployment

During Build Week, GPT-5.6 supported three major extensions:

• Breeding Assistance
• Lab-first Admin
• IACUC tracking
• Role-based Training

The system supports:

• Role-aware access
• Export to Excel
• Outlook-compatible reminders
• Anonymized deletion of inactive accounts
• Training within the application without affecting data

Evidence: Self-reported technical stack and development process. No evidence of production deployment, scalability, or performance metrics.

The author states that LABMAS has been essential for daily research activities in their own lab and colleagues’ labs. They also released a demonstration with synthetic data so judges could test the workflow during the hackathon.

However, there is no evidence of:

• Revenue
• Customers or users beyond the author’s personal experience
• Adoption metrics
• Institutional deployment
• User feedback or reviews
• Growth trends

The project was reportedly already functional before Build Week, and the author documented what was added during the competition. No data on usage frequency, retention, or impact is provided.

Evidence: Not evidenced. The description states no traction or adoption data beyond self-reporting.

The description does not mention any competitors or market context. It does not state whether LABMAS is part of a broader ecosystem or if similar tools exist in the market for managing mouse colonies in research labs.

No comparison to existing software, platforms, or tools used by researchers for colony management is made.

Evidence: Not evidenced. No competitive landscape or market positioning information provided.

• Single-developer project: The team size is listed as one (Luan Vu Lab). This raises concerns about scalability, maintenance, and long-term support.
• No verified traction: No evidence of revenue, customers, or adoption beyond the author’s self-reporting.
• Unverified claims: All descriptions are self-reported and unverified. There is no independent validation of functionality or impact.
• AI dependency: The project was largely built with AI assistance (Codex). This raises questions about code quality, maintainability, and whether the system can be independently understood or modified by others.
• Unclear business model: No pricing, licensing, or monetization strategy is described.
• Limited scope: The tool appears to focus on mouse colony management. It does not appear to integrate with broader lab operations or systems beyond its own domain.

Evidence: Inferences based on self-reported information and general project characteristics.

1. Is LABMAS currently used in production by your own lab or others? If so, how many users?
2. What is the current state of the product—fully functional, prototype, or demonstration?
3. Are there any institutional or regulatory requirements that LABMAS is designed to meet beyond what’s described?
4. How does LABMAS handle data integrity and backup in case of system failure?
5. What are your plans for scaling the platform beyond a single lab or researcher?
6. Have you considered integrating with existing lab management systems or LARC platforms?
7. What is the long-term roadmap for monetization or institutional adoption?
8. How do you ensure that AI-generated code remains maintainable and auditable?