Roadmap
What we're building, in honest order
Our north star: a LAMMPS user goes from signup to downloaded outputs in under 10 minutes, and comes back weekly without fighting infrastructure. Here's the plan, updated as priorities change.
Shipped
-
Cloudflare re-platform
ShippedWorkers, D1, R2, Queues, Pages — serverless by default.
-
Accounts & auth
ShippedEmail/password signup and login with JWT sessions.
-
Projects, files & jobs UI
ShippedThe core project → edit → run → download loop.
-
Free tier + starter CPU-hours
ShippedEmail verification unlocks a small seed of compute.
-
Stripe billing (Basic & Pro)
ShippedMonthly/yearly plans and CPU-hour credits.
Building next
-
Production LAMMPS runner
In progressA real LAMMPS container image so every job runs genuine LAMMPS, not a local mock. The gate that lets us honestly say 'production.'
-
First-job tutorial
PlannedA canonical 'first job in 10 minutes' guide, linked from the marketing site and app empty states.
-
Output previews
PlannedInline preview for common output file types — logs, images, and movies right in the job view.
-
Multi-file projects
PlannedPolish for workflows that span data files, force fields, and include files.
-
Job observability
PlannedA founder dashboard for job-failure reasons — so we fix the platform before you have to.
Later
-
Restart-file workflows
Pick up a job from a checkpoint instead of starting over.
-
Course & lab packaging
Instructor guides and isolated short jobs for teaching MD.
-
Team & org accounts
Pooled credits and shared projects for labs and small teams.
-
Collaboration
Read-only project sharing with collaborators.
What we're deliberately not building (yet)
- National-lab scale (10,000-core) production HPC parity
- Non-LAMMPS engines (GROMACS, OpenMM) in the near term
- On-prem / FedRAMP enterprise install
- A click-and-drag GUI that hides LAMMPS input language
Being specific about scope is a feature. If your workflow needs something on this list, tell us.