Products
Built in the field, available to the field. Every tool here came out of real delivery work and a genuine gap in what Canvas LMS offered out of the box.
Palette
A faster editing surface for high volume Canvas work.
● Available Now
Visit PalettePalette came out of real catalog delivery work where repeated Canvas updates were slowing teams down. It gives instructional teams a cleaner way to make broad content changes without working through every course one page at a time.
It runs in Chrome beside your Canvas session, which makes it useful when a catalog needs cleanup, standardization, or repeated revisions on a real deadline.
- Batch update Canvas content from one working view.
- Edit repeated pages, modules, and course text in minutes.
- Useful for catalog cleanup, standardization, and conversion work.
- Runs beside your existing Canvas session in Chrome.
- Built for the same real world workflows Tamitu uses in delivery.
- Available now at workwithpalette.com.
Project Meridian
An AI assistant shaped around institutional Canvas operations.
● Private Beta
Ask About MeridianProject Meridian is the product version of the internal workflows Tamitu built to move faster inside Canvas. It is designed for teams handling repeated audits, content updates, quiz work, and standards enforcement across active catalogs.
It works beside the live LMS experience, with human review before any action is applied, so teams keep control while repetitive work moves faster.
- Audit course structure, dates, links, and content health from one side panel.
- Generate and revise Canvas pages, assignments, and quiz content in context.
- Run guided workflows before a team commits changes in Canvas.
- Support designer, instructor, and admin use cases inside the same workflow set.
- Keep human approval in the loop before a workflow executes.
- Available through direct Tamitu engagements while access stays intentionally limited.
Meridian was shaped by live course operations work where speed mattered and the work still had to stay reviewable.
Suggested actions are surfaced before execution so the team can inspect the change, confirm it, and keep approval intentional.
Current access is scoped through direct Tamitu engagements so setup, fit, and workflow design stay institution specific.
Want to see where these tools fit?
We can walk through which product belongs in your workflow, how it connects to delivery work, and what a realistic next step looks like for your team.