← shagato

DeepHealth Research Lab

A medical-AI research group needs a public face for its work and a private place to do it. DeepHealth is both — the site the world sees, and the workspace the researchers actually use.

the site

Public site

for anyone

The front of the lab.

A research group is only as visible as its website. This is where the lab explains what it works on, shows the projects in progress and the papers already out, introduces the people behind them, and lists the roles it's hiring for. A blog and a news feed cover the in-between work, and anyone can subscribe to a newsletter instead of remembering to check back.

behind the login

The workspace

for the researchers

Where the work actually happens.

Behind the same login is the private half. Research groups keep each team's threads in one place, an experiments log records what was tried and how it went, and publications are drafted and tracked from idea to paper. A shared file store holds the datasets and documents that otherwise live in a dozen inboxes, and a community feed gives the lab somewhere to talk to itself. Everyone's profile doubles as their public researcher page.

Running the lab

for whoever keeps it going

The half nobody sees.

Someone keeps the team page current, decides the research areas, writes the posts, sends the newsletter, and reads through job applications. That's this — tools to manage people and what they're allowed to do, publish everything the public site shows, and see who applied to which opening, none of it needing a developer.

behind the scenes

One backend

one shared service

Everything reading from the same place.

The public site and the private workspace are two faces of one service, so a paper added in the dashboard appears on the site the moment it's saved — nothing is typed twice. It handles signing in, the uploaded files, the emails that go out, a search that reaches across everything, and a quiet record of who changed what, and it's built to keep standing when a lot of people arrive at once.

Roles decide who sees the workspace and who can publish to the public site — a visitor, a lab member, and an admin each get a different door through the same front.