Your students run full Jupyter notebooks in the browser, with NumPy, Pandas, Matplotlib, Plotly, and Panel ready to go. Each student gets their own kernel in seconds.
No JupyterHub, no containers, no IT tickets. Notebooks sit right in the course, next to readings, exercises, and the tutor.
Code cells, rich narrative, terminal output, inline plots, file uploads, and interactive widgets — all on a single page alongside the curriculum. No separate app, no context-switching.
Your students open a notebook and start coding. There’s nothing to install, and no files to collect.
No JupyterHub, Docker, or cloud compute. Python runs right in each student's browser.
Unit tests show pass or fail right in the notebook. Results go straight to the gradebook, no nbgrader needed.
Pick any student to see their notebook, code and output included.
Track runs, attempts, and time spent. Catch a stuck student early.
Notebooks sit right next to readings, exercises, and tutoring.
Code runs in a browser sandbox. It can’t reach the operating system or other students’ work.
Your students run cells, see plots, and use a terminal on any Chromebook, tablet, or school PC.
Output streams live, and input() works just like it does in a local terminal.
Students compare their edits with the starter code, line by line. Teachers see the same view.
Pick a student and see their notebook as it stands, with code and output. No files to collect.
Reviewing a notebook page? Student Journey shows how every cell on it was written.
Adjusted Gross receipts in millions of dollars. Use np.round to retain only two decimal places.
Select a learner from the dropdown to view their work.
Use the data that comes with the course, or bring your own from a file, Google Drive, or a web link.
| name | score | grade | |
|---|---|---|---|
| 0 | Alice | 92 | A |
| 1 | Brian | 78 | B+ |
| 2 | Carmen | 85 | A- |
| 3 | David | 64 | C |
Students build with ipywidgets, Panel, and language model APIs, and see the results live.
Would you like to order one of these?
A notebook page can have a dozen cells. Student Journey shows you which one a student struggled with, and opens it.
A scripted walkthrough with sample data, not live student work. Teachers use these same panels.
Other platforms keep versions of a file. Alps keeps the history of every cell.
Every Alps coding activity has the same replay. See Process Insights
Assign a notebook and your students are coding in minutes. No setup, and no files to hand out.
Have your own Jupyter Book? Our team can bring it onto Alps. Its Python cells run right in the browser, unless a cell needs a library the browser can’t load. See how a book gets onto Alps.
See how notebooks on Alps compare with a traditional Jupyter setup.
| Feature | Alps | Other platforms |
|---|---|---|
| No setup: open a browser and start coding | ||
| Works on Chromebooks and tablets | ~ | |
| No kernel cost per student | ||
| ~2 second kernel startup | ||
| See any student’s work in one click | ||
| Notebooks built into the course | ||
| Progress analytics and attempt tracking | ||
| Student Journey: every cell on a notebook page in one view | ||
| Replay of how each cell was written | ~ | |
| Line-by-line diff against the starter code | ||
| Secure browser sandbox with no OS access | ~ | |
| Upload files or open them from Google Drive | ~ | |
| NumPy, Pandas, Matplotlib, Plotly | ||
| ipywidgets with real-time callbacks | ||
| IPython magics (%pip, %timeit, %who) |
Notebooks that run in the browser, with grading and progress tracking built in.