Composer · Music composition & engraving · On our own engine · Early access · 2026
Composer is the composition front of an owned music engine. You build a score in the composition builder — parts, measures, notes, chords, ties, dynamics, and articulations, checked as you go. The engraver sets the notes and renders native SVG. Re-time changes the meter of a passage without re-entering it, transpose shifts its pitch, and you can import a score you already wrote to keep editing it. All of that runs on our own engine — no desktop notation program and no third-party notation service in the path. The engine is delivered and gate-verified. The in-the-style-of arranger, playback, MIDI and PDF export, and the live composer app in a browser tab are on the roadmap, riding the engraver WASM seam being wired in now — we say so plainly. Composer does not compose for you: there is no AI-generated music here, and what you write is your own.
Our own engine — the whole path from note entry to an engraved page is ours
Most ways to notate music lean on a program someone else built: a desktop package you buy and install, or a browser editor run as an outside service. That means the engraving and the export you depend on belong to a company that is not you, and the file formats and the roadmap belong to them too.
Composer is built the other way. The composition builder, the engraver that renders SVG, re-time, transpose, and import are all our own delivered, gate-verified code, on one engine. Nothing in the chain from the notes you enter to the engraved page is a third-party notation program. The engine is also built around a transform seam — any tool that takes a score and returns a score plugs in and is re-checked on the way through — which is how re-time and transpose ride it, and how the in-the-style-of arranger will when it lands.
The engine is delivered today. What is still being built is the live in-browser app — the tab at composer.software where you do all of this without installing anything — which rides the engraver WASM seam being wired in now, along with the arranger, playback, MIDI, and PDF export. We would rather tell you exactly where that line sits than dress in-progress work up as finished.
How it works
Composer runs on the composing arc: build the score, reshape it with re-time and transpose (or import one you already wrote), engrave it to the page, then save it. Each stage is described as it is built today — the engine is delivered, and the arranger, playback, MIDI, PDF, and the live in-browser app are on the roadmap.
Step 1 · Build the score — parts, measures, notes, chords, ties, dynamics, and articulations
You build the score in the composition builder: add the parts and clefs, open a measure, and place the notes, chords, and rests, with ties, dynamics, and articulations attached where they belong. The builder computes each event’s timing and checks the structure as you go, so a mistake is caught rather than passed through silently. The builder is the delivered composition engine.
Step 2 · Re-time, transpose, and import — reshape it without retyping
Change the meter of a passage and the notes regroup into the new bars, note sequence and total duration preserved — fail-closed if a note would straddle a barline. Transpose shifts the pitch by a number of steps. And a score you already wrote can be imported straight into the builder to keep editing. Re-time, transpose, and import are all delivered and gate-verified.
Step 3 · Engrave it to the page — native SVG, on our own engine
The engraver sets the notes — spacing, beams, stems, ties, and how systems break across the page — and renders the score as native SVG, a clean vector page to view and print. It runs on our own engine, with no desktop notation program and no third-party notation service in the path. The engraver is delivered.
Step 4 · Save and re-open — a portable score file, yours to keep
Save the score to a portable file that re-opens and round-trips exactly, so you can put it down and pick it back up with nothing lost. The engraved SVG and the portable score file are what leave Composer today; playback, MIDI, and PDF export are on the roadmap. Your score and your files are yours — open formats you can take anywhere.
What it does
Every capability is labelled plainly: Built means the engine capability is delivered and gate-verified. In development means the tool or surface is on the roadmap and not delivered. We do not claim otherwise.
The composition builder is where a score takes shape. You add parts and clefs, open a measure, and place notes, chords, and rests with their pitches and rhythms — and the builder computes each event’s timing for you and holds the whole thing as one structured score. Ties, slurs, dynamics, and articulations attach to the notes they belong to. You can seed the builder from a score you already have and keep editing it. Every build is checked: a structural mistake is caught and reported rather than passed through silently. The builder is delivered and gate-verified code — the composition engine this whole surface is built on.
Built · the delivered composition engine
Once a score is built, the engraver sets it: note spacing, beam grouping, stem direction, ties, and how systems break across the page — the typesetting work that separates a page a performer trusts from one they squint at. It renders that page as native SVG, a clean vector page you can view and print. This runs on our own engraving engine: there is no desktop notation program and no third-party notation service anywhere in the path. The engraver is delivered and gate-verified.
Built · native SVG, our own engine
Re-time changes the meter of a passage: give it a new time signature and it regroups the events into bars of the new meter, keeping the note sequence and the total duration exactly the same. It is fail-closed — if a note would straddle a new barline it tells you rather than quietly mangle the music. Transpose shifts every pitch by a number of steps, leaving rhythm and meter untouched. Both work on the score you already entered, so you reshape it without retyping. Re-time and transpose are delivered and gate-verified.
Built · meter change and transpose, fail-closed
Composer can import an existing text score and hand it straight to the builder, so you can take something you already wrote and keep editing it here. And a score saves to a portable file that re-opens and round-trips exactly — the same music comes back, ready to keep working on, with nothing lost in translation. Import and the portable score file are delivered and gate-verified. They keep your work yours: open formats in, open formats out.
Built · import in, portable score file out
Composer is built around a transform seam: any tool that takes a score and returns a score plugs into it, re-checked for correctness on the way through — re-time and transpose already ride that seam. The in-the-style-of arranger, which would set a melody in the style of a genre from your own material, plugs into that same seam. The seam is delivered; the arranger tool itself is on the roadmap, not delivered today, and this page does not claim it is. When it lands, it will work from your material, not compose a piece from a prompt.
In development · the seam is built, the arranger is on the roadmap
The engraver renders native SVG today. Hearing the score played back, exporting a standard MIDI file, and exporting a PDF are on the roadmap — they are not delivered today, and this page does not claim they are. They will render the notes you wrote, never invent new material. Until they land, SVG and the portable score file are how work leaves Composer.
In development · SVG ships today; MIDI, PDF, and playback are on the roadmap
The engine is delivered. The live composer app that puts it in a browser tab — where you build, engrave, re-time, transpose, and import without installing anything — rides the engraver WASM seam being wired in now. That in-browser experience is in active development, and this page does not claim the browser app is usable today. When it is ready, early access is how you get in first; until then, the honest next step is to ask.
In active development · the browser app is being wired in
Who it is for
You build the score in the composition builder and engrave it to a clean SVG page for your players. Re-time lets you try the same music in a different meter without re-entering it, transpose shifts the whole thing by a few steps, and a score you already wrote imports straight in to keep editing. Your work saves to a portable file that re-opens exactly, and exports as SVG — the score you wrote, in your hands.
A student can notate an assignment and engrave it into a clean page — on an engine that keeps the work theirs. There is no AI writing the music for them: they place the notes, and the tool sets and checks what they wrote. What they compose is their own, and it saves and exports in open formats.
A teacher or program can put one composition tool in front of students that covers building, engraving, re-time, transpose, and import — without buying and installing a desktop notation program per seat. The engine is delivered; the live in-browser app is being wired in, and early access is how a program gets in first. Student work stays the student’s own.
Your music is your own
The music you make on Composer is your own composition. The engine has an AI continuation seam, but it is honest-off: it is disabled by default, no model is wired to it, and no code path fabricates notes. There is no AI-composed audio anywhere in the product, and the in-the-style-of arranger, when it lands, will work from your own material rather than generate a piece from a prompt.
The platform claims no license to your compositions beyond what it needs to store them and produce the formats you ask for. Nothing you write is sold, licensed to outside parties, or used to train models. Your work leaves with you as native SVG and a portable score file that re-opens exactly — open formats you can carry anywhere.
What is delivered and what is on the roadmap — plainly stated
Delivered and gate-verified today: the composition builder (build a score from parts, measures, notes, chords, and rests, with ties, dynamics, and articulations, checked as you go, and seed-from-an-existing-score to keep editing); the engraver (sets the notes and renders native SVG on our own engine); re-time (a fail-closed meter change) and transpose (a pitch shift); and import plus a portable score file that round-trips exactly. All of it on one owned engine, with no third-party notation software in the path.
On the roadmap, not delivered today: the in-the-style-of arranger (the transform seam it plugs into is built; the arranger tool is not); playback, a standard MIDI export, and a PDF export (the engraver renders SVG today); and the live in-browser composer app at composer.software — the tab where you do all of this without installing anything — which rides the engraver WASM seam being wired in now. It is not the live in-browser experience yet, and we do not claim it is. Accounts and payment are honest-off: there is no pricing, no checkout, no billing, and no subscription on this page, because that side is being built separately. The honest next step is to ask about early access, not to check out. We say all of this directly because composers deserve to know exactly what is delivered and what is still being finished.
Part of the owned music suite
Composer is where you build and engrave. musique.software is the wider owned music suite it belongs to — the notation side plus a multitrack audio side for recording and mixing. musicschool.software runs a music program: lessons, studios, scheduling, and enrollment — adjacent, not the same product, because that runs the school while Composer is the tool a musician writes with. composition.software is the sibling writing desk for student authors, for text rather than music. All of them sit on homeroom.software, the platform.
Early access · Composers, arrangers, students, and music programs
The composition engine is delivered, and the live in-browser app is being wired in. There is no subscription, no per-seat fee, and no billing interface on this page: accounts and payment are being built separately. Asking about early access puts you in line for the in-browser app while it is finished and lets us walk through the engine honestly — the builder, the engraver, re-time, transpose, and import — and where the arranger, playback, MIDI, and PDF export sit on the roadmap. No pricing commitment, and no checkout.
To ask about early access: [email protected].
FAQ
Composer is the browser composition surface built on our own native composition and engraving engine. You build a score, engrave it to native SVG, re-time and transpose it, and import and re-open portable score files. The engine — the composition builder, the engraver, re-time, transpose, and import — is delivered and gate-verified. The in-the-style-of arranger, playback, MIDI and PDF export, and the live in-browser app are on the roadmap, and this page says so plainly.
Not yet. The composition engine is delivered, but the live app at composer.software — the browser experience where you build, engrave, re-time, transpose, and import without installing anything — rides the engraver WASM seam being wired in now, so it is in active development. This page describes what the engine does and where the app is going; it does not claim a working in-browser product today. Ask about early access to get in first.
The composition builder is the delivered engine that constructs a score from its parts: you add parts and clefs, open measures, and place notes, chords, and rests, with ties, slurs, dynamics, and articulations. It computes each event’s timing and checks the structure as you build, so a structural mistake is caught and reported rather than passed through. You can also seed the builder from a score you already have and keep editing it.
No. The building, engraving, re-time, transpose, and import all run on our own owned engine. There is no desktop notation program to buy and install, and no third-party notation service in the path. The whole chain from the notes you enter to the engraved page is ours.
Today the engraver renders native SVG, a clean vector page to view and print, and a score saves to a portable file that re-opens and round-trips exactly. Playback, a standard MIDI export, and a PDF export are on the roadmap — they are not delivered today, and this page does not claim they are. What ships today is what this page counts as built.
It is on the roadmap, not delivered. Composer is built around a transform seam — any tool that takes a score and returns a score plugs in and is re-checked on the way through, and re-time and transpose already ride it. The in-the-style-of arranger, which would set a melody in the style of a genre from your own material, plugs into that same seam. The seam is delivered; the arranger tool is not built yet. When it lands it will work from your material, not compose a piece from a text prompt.
No. Composer is a tool you use to write your own music. The engine has a continuation seam, but it is honest-off: it is disabled by default, no model is wired to it, and no code path fabricates notes. There is no AI-composed audio anywhere in the product. What you make is your own composition.
Re-time changes the meter of a passage: give it a new time signature and it regroups the events into bars of the new meter, keeping the note sequence and total duration exactly the same, and it is fail-closed — if a note would straddle a new barline it tells you rather than mangle the music. Transpose shifts every pitch by a number of steps, leaving rhythm and meter untouched. Both are delivered and work on the score you already entered.
There is no pricing and no checkout on this page. Accounts and payment are being built separately; today the honest next step is to ask about early access, not to check out. No billing, no subscription, and no contract are presented here.
You do. The platform claims no license to your compositions beyond what it needs to store them and produce the formats you ask for. Nothing you write is sold, licensed to outside parties, or used to train models, and no AI-generated music is produced. Your work exports as native SVG and a portable score file so you can leave with all of it.
Composer is the composition and engraving front: build, engrave, re-time, transpose, and import. musique.software is the wider owned music suite it belongs to — the notation side plus a multitrack audio side for recording and mixing. musicschool.software runs a music program: lessons, studios, and enrollment. All on the same platform, homeroom.software.