Cadence for iPhone and Android is in testing. Become a tester
We believe that the deep integration of hardware and software is the key to making technology intuitive and beautiful.
Now testing on iPhone and Android
Your campus. Your schedule. Your people.
Products
Four apps, one account, one platform. Built to be used together.
Across every product, Noctic is exploring a practical AI layer that can reason over your context, use tools carefully, explain its work and stay under your control.
Shiba
Parable 4.5 reasoning, Agent Mode, effort tiers, code artifacts, images, voice and memory.
Cadence
Feed, reels, calendar, notes, channels, DMs and verified school registration.
Compass
A study hub that reads Cadence data, plans short, and tutors the gaps.
Momentum
A glowing streak matrix, a 30-second evening check-in, and private on-device storage.
Usync
Files between your own devices in a browser tab, and between people from a Mac or an iPhone — encrypted before anything leaves the machine.
Kick Start
Next.js 15 with authentication, Stripe billing, workspaces and a dashboard already wired together. $199 USD, paid once, downloaded with a code.
Concept
Two desktop-class computers, Aeon™ and Aeon™ Neo, and two Aebook™ laptops, Nano and Pro — from an 8 GB fanless N100 laptop to a twenty-four-core desktop, all running a custom Linux with the Glass UX.
Its AI layer is designed for useful, explainable assistance: find a document, summarise a project, surface the next action and let you approve important changes.
Concept
Our own x86-64 processor family, Aether. The most ambitious project here and the one furthest from existing — no silicon, no foundry, no date.
The page covers how the chip would work, how it would be made, what each stage costs, and the list of reasons it might never happen.
Noctic Account
Identity, plan, privacy and OAuth — the seam between every product.
Noctic Platform
Shared auth, billing, rate limits, storage, AI gateway and security policies. Every product inherits it for free.
They overlap on purpose, so the honest answer depends on what you are trying to do this afternoon rather than on which is most capable.
| Shiba | You have a problem to think through, something to write, code to work on, or a question with more than one right answer. Start here — everything else is built on the same reasoning. |
|---|---|
| Cadence | You are at a school and need the day in one place: the feed, the calendar, notes, channels and messages, with verified registration so you know who you are talking to. |
| Compass | You know what you have to learn and not how to fit it in. It reads your Cadence data, plans in short blocks and tutors the parts you keep getting wrong. |
| Momentum | You want to keep at something daily and see the evidence. A thirty-second evening check-in, stored on your own device. |
The reason to build several products rather than one is that the hard parts are common to all of them. Each app inherits the same foundations, so an improvement in one is an improvement everywhere.
Sign in once. Your identity, plan and privacy choices follow you into every product.
The same reasoning model behind Shiba answers in Cadence and plans in Compass.
The same privacy policy, the same safety work and the same limits on what an app may ask for.
Export everything, or delete the account and its content across every product, from Settings.
No. Each works on its own, and none of them nags you about the others. They get better together because they can read each other's context, not because anything is withheld until you sign up twice.
Yes, on every product. The full breakdown of what each plan includes is on the pricing page.
Not unless you turn it on. It is off by default in Settings, and turning it off again stops future use immediately.
A Noctic Account requires you to be at least 13. What we do differently for younger and school-age users is set out under children and teens.
Yes. Continue with Noctic is open to apps that are not ours, and the tools to wire it up are in the developer section.
Download · $199 USD, paid once
The SaaS starter we build on, as a zip. Next.js 15, authentication, billing, multi-tenant workspaces and a dashboard — wired together, typed end to end, and unbranded so you can ship it as your own.
Not a template you pull apart. A working product with your name missing from it.
What is in the zip
JWT sessions in httpOnly cookies with server-side session records, so revocation is instant. Email and password, Google and GitHub over PKCE, protected-route middleware and role-based guards.
Stripe Checkout and the customer portal, webhooks that verify signatures and survive being delivered twice, tables for subscriptions and one-off payments, and plan entitlements.
A Drizzle schema for users, OAuth accounts, sessions, organisations, members, invitations, subscriptions and payments — with the SQL migrations already generated.
A token-driven component library: buttons, cards, inputs, tables, modals, dropdowns, toasts, avatars and badges. Dark and light, responsive, no framework to learn on top of Tailwind.
Collapsible sidebar, workspace switcher, user menu, theme switching with no flash on load, and the settings, team and billing pages already written against the schema.
npm run typecheck and npm run build both pass on a fresh unzip. Three
environment variables boot it; everything else stays disabled until you add its keys.
Next.js 15 with the App Router, TypeScript, Tailwind CSS, Drizzle ORM, PostgreSQL and Stripe. The zip is
the source tree, not a node_modules dump — unzip it and run npm install.
There is no checkout on this page and no card form to fill in. You send the money from your own bank, we send back a code, the code opens the download.
$199 USD, once
Send it to
nicholassteiche@icloud.com
Security question, if your bank asks for one
What kit is this
Answer
kickstart20
Interac e-Transfer to nicholassteiche@icloud.com. If your bank asks for a security question, use the one above: What kit is this, answered kickstart20, lower case and no space.
Write the address on your Noctic Account in the transfer's message field. That is where the code is sent, and the account it belongs to.
Once the transfer lands in the bank we email you a code of your own. It looks like
KS-A7QF-2M4X-9KDP-3TWE, and no one else is ever given it.
Enter the code below and the zip downloads. The code is used up in the act, so save the file rather than the code.
Paying from outside Canada, or in a currency your bank will not e-Transfer? Write to support and we will sort out another way to take the $199.
Sign in first — the code is issued to your account. Entering it spends it and opens a private link that lasts fifteen minutes, so download the zip and keep it: a code that has been used is used for good, including for anyone it gets forwarded to.
Your code is spent
Kick Start is yours. Save the zip somewhere you will find it again — unzip it, run
npm install, copy .env.example to .env.local, and the README
takes it from there.
| The whole source | Every file, readable and editable. Nothing is minified, obfuscated or held back for a higher tier. |
|---|---|
| Unlimited projects | Build as many products on it as you like, for yourself or for clients, and charge whatever you charge. One purchase covers all of them. |
| Not for resale as a kit | Ship what you build with it. Do not repackage the kit itself, changed or unchanged, as a starter for other people to buy or download. |
| No subscription | One payment. There is no renewal and no seat count. What you download is yours to keep and to build on for as long as you like. |
| Support is best effort | Ask us anything at contact. This is a zip, not a managed service, so treat any answer as a favour rather than an entitlement. |
| No refunds after the code | The code is the product, and it cannot be returned once it is sent. If something in the kit is genuinely broken, tell us and we will fix it or refund you. |
Because a card checkout here would mean holding a payment integration for a single product. An e-Transfer costs you nothing, clears the same day, and does not put your card details in front of us at all.
A few hours in practice, one business day at worst. Transfers are read by a person, so an overnight payment is answered in the morning rather than the moment it lands.
Send the Canadian equivalent of $199 USD on the day you pay. Any small gap either way from the rate is fine; we are not going to chase a dollar over it.
Check it character for character — there is no letter I or O, and no digit 0 or 1, in a code, so those are usually the typo. Spaces and lower case are fine. If it still fails, reply to the email the code came in.
No, and that is the point — a code that has been spent is dead for everyone, so a forwarded one is worth nothing. For the first day after you use it we will still hand you a fresh link if a download drops halfway. After that, ask us and we will open it again.
No. Kick Start is sold and delivered entirely outside the account system. Nothing about this purchase touches your Noctic Account if you have one.
Dependencies, which npm install fetches; a database, which you point
DATABASE_URL at; and your Stripe and OAuth keys. The README lists every variable and
what it switches on.
What you download is the build of the day, and the code will not open a later one. Write to us if you want the current kit again and we will send a fresh code. There is no changelog feed and no upgrade path back into a project you have already changed.
In development
Encrypted before it leaves your machine. Usync moves files between your own devices in a browser tab. Usync Air moves them between people, from a Mac or an iPhone, without either file ever being readable by anything in the middle.
AirDrop only works when both machines are in the same room. Email attachments are read by every server they touch. This is the third thing.
Two halves
Usync
A browser tab on every machine you own. Drop files, a folder, a block of text or a link into one and it lands on another — no cable, no account juggling, no emailing yourself.
Names the devices, remembers the ones you use, and works from a phone browser as readily as from a desktop. Included with a Noctic Account.
Usync Air
Native apps for macOS and iPhone that send to approved contacts. Watched folders, team spaces, and a relay that holds ciphertext for as long as it takes the other side to collect it.
$10 a month. Universal on Apple silicon and Intel, iOS 16 or later.
Security
Files that land on a machine by themselves are how machines get ruined. So a security code lets somebody reach you. It never lets them write to you. That takes your approval, once, per person.
Sixteen characters, generated for you and never chosen. Share it like a phone number. Roll it the moment it leaks and the old one dies instantly.
That pair finds a person and asks to connect. It moves zero bytes. Wrong guesses are rate limited and look identical to misses, so codes cannot be fished out one attempt at a time.
Both sides agree before the database permits a single transfer. Auto-download then runs only for approved contacts, and only under the ceiling you set.
Everything is sealed on your device before it is uploaded. What passes through is ciphertext and a checksum, and it is deleted the moment it is collected.
Five steps, none of which involve a server that could read anything even if it wanted to.
| 1 · Sealed | The sender's device generates a one-time key and encrypts the file with AES-256-GCM. The key exists for this one transfer and is never reused. |
|---|---|
| 2 · Wrapped | That key is wrapped for the recipient using X25519 key agreement, so only their device can unwrap it. Private keys live in the Keychain and never leave the machine they were made on. |
| 3 · Relayed | The ciphertext goes to the relay, which holds no key and can decrypt nothing. It is a corridor, not a filing cabinet. |
| 4 · Verified | The recipient downloads, unwraps, decrypts, and recomputes the SHA-256. A mismatch is discarded rather than saved — a half-arrived file is not a file. |
| 5 · Wiped | Once collected, the object is deleted from the relay. Nothing accumulates that could later leak. |
What you get
Point Usync Air at a folder. Save a file into it and the file is already on the other machine. No button, no upload dialog, no remembering to send it.
Chosen per contact. People you trust land in a folder. Everyone else waits in an inbox until you say so, however much they send.
Group your people. Drop a file once and it reaches everyone approved in the space.
Every transfer carries a SHA-256 checksum, recomputed after decryption. A mismatch is refused, not opened.
Nothing needs to be on the same Wi-Fi, in the same building or on the same continent. If both machines can reach the internet, they can reach each other.
The same Noctic Account that carries Shiba and Cadence. Sign in once and the apps know who you are.
Some settings are yours to choose. These are not, because the whole point of an automatic download is that you are not there to catch it.
| Executables never auto-save | Whatever auto-download says, anything on the refused list waits for you to look at it. The list is in the app, not a server setting somebody else can edit. |
|---|---|
| Quarantine is kept | Files written to disk keep the flag macOS puts on downloads, so the operating system still asks its own questions before anything runs. |
| Your size cap holds | Anything over the ceiling you set waits in the inbox instead of filling a disk while you sleep. |
| Approval is per person | Approving one contact approves that contact. There is no setting that opens you to everybody, because we did not build one. |
| Keys stay on the device | Private keys are generated in and never leave the Keychain. We cannot read your transfers, and there is no key escrow to be compelled for. |
Included with a Noctic Account
$10 USD / month
Downloads are tied to the account and the plan, so a build cannot be passed around. Payment is handled by Stripe and card details never reach our systems — the same arrangement as everything else on the pricing page.
Where it actually is
The apps are real and they build. What is not yet true is everything behind them, and it would be easy to write this page as though it were.
macOS compiles in release and ships as a disk image. iOS runs. The encryption, the contact model and the safety rules above are written, not sketched.
The database schema and the functions that turn a Noctic sign-in into a session are written and not yet live. Every call fails with a specific message rather than pretending.
Until it is signed and notarised, macOS will refuse it on any machine but the one that built it. That is the last step before anyone else can run this.
A limit of the current storage plan, not the design. Resumable chunked upload is the next piece of work and lifts it.
No, and not as a promise — as an arrangement. The key that opens a file is created on your device and wrapped so that only the recipient's device can unwrap it. What we hold is ciphertext we have no key for, briefly, and then not at all.
The private key goes with it, which means transfers sent to that device and not yet collected cannot be opened by anything. Set up a new device and ask the sender to send again. There is no recovery key, because a recovery key is a key somebody else can be made to hand over.
Ask to connect. That is the whole list. Until you approve them the database refuses every transfer, and you can roll the code from the app, which kills the old one immediately.
AirDrop needs both machines nearby and both to be Apple. This needs an internet connection and an approved contact. The overlap is smaller than it sounds.
No. The browser half stands alone and covers sending things to your own devices, which is most of what most people want. Air is for sending to other people.
Not yet, and not soon. The browser half runs anywhere; the native apps are macOS and iOS because that is where the Keychain work is done and where we can test properly.
When the backend is deployed and the installer is signed. Both are in the list above, and neither has a date attached, because a date we cannot keep is worse than no date.
Concept · indicative pricing, buying locked until 2030
Two desktops, Aeon™ and Aeon™ Neo, and two laptops, Aebook™ Nano and Aebook™ Pro. The same AXESS OS on all four, made to make Linux feel obvious.
From $499 to $3,499. Aebook™ Nano pricing is final; the other three are indicative until release in 2030.
Aeon™ is the family, and the name of the desktops. The laptops are Aebook™. The same AXESS OS, the same Glass UI and the same x86-64 architecture run on all four, so you are choosing a shape and how much work it can take, not which features you are allowed to have.
Desktop · small and portable · concept
Desktop-class, fifteen centimetres square.
Carry it between desks and run it from a USB-C charger. Sixteen cores under a vapour chamber, in something you can hold in one hand.
Not for: working away from a desk. There is no screen and no battery.
Desktop · full size · concept
Twenty-four cores. One fan, barely turning.
Sixty-four gigabytes on one desk, cooled by a single large fan that rarely has to work, with six USB-C ports and room for four displays.
Not for: games or work that needs a graphics card. There is no slot for one.
Laptop · the economical one · October 2026
Light, silent, and cheap to replace.
A first computer, a school computer, or a second one. It is the first machine in the family being made, and the only price on this page that is final.
Not for: editing, gaming, compiling, or forty tabs. It is honest about being small.
Laptop · the fastest one · concept
Everything the Neo does, with a screen and a battery.
Sixteen cores, a 16.2-inch 144 Hz screen and a vapour chamber, for work that has to travel and cannot slow down when it does.
Good for: heavy work away from a desk, in the room or on the way to it.
Desktop-class, small enough to carry.
From $1,499 indicative
Its page
Twenty-four cores, sixty-four gigabytes.
From $2,499 indicative
Its pageIf you work at a desk, the Aeon™ Neo, for most people, and the Aeon™ if you already know you need twenty-four cores. If the machine has to go with you, the Aebook™ Pro — or the Aebook™ Nano if the price is what decides it. If none of that lands, seven questions will get you closer than a specification table will.
Because Aeon™ is the name of the family and of the desktops, and a laptop deserves a name that says what it is. An Aebook™ is still an Aeon™ underneath: the same system, the same architecture and the same rules.
They are gone. Two laptops at either end of the range and two desktops between them cover the same people with far less overlap. If you reserved one, reply to your confirmation email and tell us which machine you would like instead.
A four-core Intel N100, 8 GB of memory, 64 GB or 500 GB of storage, a 12.5-inch 60 Hz screen and an aluminium body instead of titanium. It exists so that AXESS OS can be put in front of someone who is not going to spend a lot of money on a computer, and it runs the same system as the other three. The whole machine is on its own page, ceilings included.
Intel’s. The Aeon™ Neo and Aebook™ Pro use a Core Ultra 9 285H, the Aeon™ a desktop Core Ultra 9 285, and the Aebook™ Nano an N100. We intend to replace the Core Ultra parts with our own x86-64 silicon eventually, which is a much longer story told on the Noctic Silicon page.
Not for you. Both are x86-64, so it is the same AXESS OS build, the same software and the same packages. A processor transition is usually an event everybody who owns the machine has to live through. This one would be an internal detail.
No, not even on the desktops. Memory is soldered beside the processor on every machine in the family. Buy the size you will still want in four years.
Really. USB-C carries display out, so a single cable or a hub covers it. If that is a dealbreaker, it is a fair one and this is not the family for you.
AXESS OS is Linux, so standard AppImage packages are planned to work and the terminal is there. What we are changing is the assumption that you must use it.
The Aebook™ Nano is taking orders for October 2026. The other three are not for sale yet: you can reserve a spot in the first hundred, which costs nothing and commits you to nothing.
Seven questions, and a straight answer at the end of them — including “none of these”.
Answer themThe whole plan for building our own x86-64 chips, including the ways it could fail.
Read the planThe first hundred, for the three machines that are not for sale yet. It costs nothing.
Reserve oneWhat every control in AXESS OS is drawn with, and the rules behind it.
See GlassAnything this page did not answer, including whether the Nano is enough for you.
Get in touchWhat AXESS OS collects, which is nothing you have not switched on yourself.
How privacy worksThe Aebook™ Nano exists partly for classrooms. This is the rest of it.
Noctic for EducationEvery decision about this family, dated, including the ones we reversed.
Read the changelogPlanned figures for machines that are mostly unbuilt. Every one of them may change.
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Processor | Intel Core Ultra 9 285H | Intel Core Ultra 9 285 | Intel Processor N100 | Intel Core Ultra 9 285H |
| Platform | Core Ultra 200H series | Core Ultra 200S series | Alder Lake-N | Core Ultra 200H series |
| CPU cores | 16 — 6P + 8E + 2LP-E | 24 — 8P + 16E | 4 — 4E | 16 — 6P + 8E + 2LP-E |
| Threads | 16 | 24 | 4 | 16 |
| Max turbo | 5.4 GHz | 5.6 GHz | 3.4 GHz | 5.4 GHz |
| L3 cache | 24 MB | 36 MB | 6 MB | 24 MB |
| Graphics | Arc 140T · 8 Xe cores | Intel Graphics · 4 Xe cores | UHD Graphics · 24 EU | Arc 140T · 8 Xe cores |
| Neural engine | NPU 3 · 13 TOPS | AI Boost NPU · 13 TOPS | None | NPU 3 · 13 TOPS |
| Memory | 32 GB soldered | 64 GB soldered | 8 GB soldered | 32 GB soldered |
| Memory speed | LPDDR5X-8400 | DDR5-5600 | LPDDR5-4800 | LPDDR5X-8400 |
| Upgradeable | No. Memory and storage are fixed when the machine is made, on all four. | |||
Intel, Core Ultra and Arc are trademarks of Intel Corporation. Noctic has no partnership, endorsement or supply agreement with Intel. These are the parts machines like these would be built around if they were built today, chosen from a public price list like anyone else’s.
Aether is our own x86-64 family: three parts, one architecture, so a single build of AXESS OS runs on all of them. None of it exists. Every figure below is a target written into a specification rather than a measurement taken from a chip.
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Chip | Aether A1 | Aether A2 Max | None — stays on Intel N-series | Aether A2 Max |
| CPU cores | 8 — 4P + 4E | 24 — 8P + 16E | — | 24 — 8P + 16E |
| Threads | 8 | 24 | — | 24 |
| Max turbo | 3.8 GHz | 5.7 GHz | — | 5.7 GHz |
| L3 cache | 18 MB | 36 MB | — | 36 MB |
| GPU cores | 10 | 24 | — | 24 |
| Neural engine | 16-core · 24 TOPS | 32-core · 48 TOPS | — | 32-core · 48 TOPS |
| Memory | 16 GB LPDDR5X | 16 GB | — | 16 GB |
| Memory bandwidth | 153 GB/s | 205 GB/s | — | 205 GB/s |
| Status | Specification only. Not designed, not verified, not manufactured, no date. | Releasing October 2026, orders open now. | Specification only. | |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Display | None — bring your own, over USB-C | 12.5-inch, 1920 × 1200 IPS, matte, 60 Hz, 400 nits | 16.2-inch 8K Ultra Retina XDR, 144 Hz, 1600 nits peak | |
| Colour | Whatever your display shows | sRGB, 8-bit | P3 wide gamut, 10-bit, factory calibrated | |
| Touch and unlock | Password, PIN, or a paired Aebook™ | No touch · password or PIN | Multi-touch · face unlock | |
| Keyboard | Not included — any USB-C or Bluetooth keyboard | 1.3 mm travel, not backlit, with the Aeon™ key | Backlit, 1.5 mm travel, with the Aeon™ key | |
| Camera | None | 1080p, in the top bezel | 12 MP, in the Dynamic Notch | |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Storage | 1 TB NVMe · 2 or 4 TB to order | 2 TB PCIe 5.0 NVMe · 4 or 8 TB to order | 64 GB eMMC or 500 GB NVMe | 2 TB PCIe 5.0 NVMe · 4 or 8 TB to order |
| Sequential read | Around 7 GB/s | Around 14 GB/s | 0.3 GB/s or 2.2 GB/s | 7.4 GB/s |
| Power | USB-C, 140 W adapter | USB-C, 240 W adapter | 42 Wh battery · 45 W USB-C | 100 Wh battery · 96 W USB-C |
| Battery life | No battery | Up to 14 h | Up to 16 h | |
| Cooling | Vapour chamber and one quiet fan | Vapour chamber and one 140 mm fan | Vapour chamber, no fan | Vapour chamber and two fans |
| Size | 15 × 15 × 6 cm | 16 × 16 × 27 cm | 12.5-inch · 15.4 mm thick | 16.2-inch · 16.8 mm thick |
| Weight | 1.5 kg | 4.1 kg | 1.02 kg | 2.14 kg |
| Body | Aluminium unibody | Aluminium | Anodised aluminium | Titanium-and-aluminium unibody |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| USB-C ports | 4 | 6 | 2 | 4 |
| Per-port bandwidth | USB4 · 40 Gb/s | USB4 · 40 Gb/s | USB 3.2 Gen 2 · 10 Gb/s | USB4 v2 · 80 Gb/s |
| External displays | Three, up to 6K | Four, one at 8K | One 4K | Three 6K or one 8K |
| Power | USB-C, 140 W | USB-C, 240 W | USB-C, 45 W | USB-C, 96 W |
| Wireless | Wi-Fi 7 and Bluetooth 6.0 | Wi-Fi 7 and Bluetooth 6.0 | Wi-Fi 6E and Bluetooth 5.3 | Wi-Fi 7 and Bluetooth 6.0 |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Speakers | One, for alerts | Two | Six with dual subwoofers | |
| Microphones | None | Two | Four, studio array | |
| System | AXESS OS — Linux-based, Glass UI, AppImage support | |||
| Telemetry | None unless you switch it on | |||
| Warranty | Intended at two years, parts and labour | |||
| From | $1,499, indicative | $2,499, indicative | $499, final | $3,499, indicative |
| Its own page | Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro |
Concept status: the Aeon™, Aeon™ Neo and Aebook™ Pro are concepts. Nothing has been manufactured, there is no manufacturing partner and no release date. Their prices in the builder are indicative, and buying is locked until release, which we do not expect before 2030. The processor choice, memory, storage, display, battery, cooling, body and every other hardware and software detail on this page is planned rather than final, and may change or be abandoned. Intel, Core Ultra and Arc are trademarks of Intel Corporation; Noctic has no partnership with or endorsement from Intel. The Aether A1 X Nano, A1 and A2 Max are specifications for silicon that does not exist — see Noctic Silicon.
Releasing October 2026 · final pricing, orders open now
The cheapest machine we could design without it being a bad one. Intel N100, 8 GB of memory, no fan, and the same AXESS OS as the other three.
From $499. Now accepting orders. Shipping October 2026 or earlier.
The point of it
Every other machine in the lineup is a premium machine. This one is not, deliberately, and it is the only honest way to put AXESS OS in front of a student, a classroom or anyone who simply does not want to spend a lot of money on a laptop.
The Aebook™ Nano is built around a processor that costs a fraction of the others, a body made of anodised aluminium rather than titanium, and a screen chosen for being good rather than for being remarkable. What it does not do is cut the software. It runs the same build of AXESS OS, gets the same updates on the same day, and collects no more data about you than the Pro does — which is none.
Browsing, email, documents, spreadsheets that a person made rather than a bank, calls, note-taking, streaming, homework, coursework, and being carried around all day without a charger.
Video editing, 3D, gaming beyond what a browser does, large compiles, virtual machines, or forty browser tabs at once. It will attempt all of these and you will notice it trying.
Four cores, four threads and 8 GB. Around twenty-five tabs and a document is a comfortable day. Past that the machine starts swapping and you start waiting. We would rather write that down than have you discover it in week three.
Six watts of base power means no fan, no vents that whirr in a quiet room, and nothing inside that can fail mechanically. Fanless on the Nano is a consequence of the chip, not a feat of engineering. A thin vapour chamber — a sealed plate with a little liquid inside that boils off the hot chip and condenses at the cool edges, moving heat like a tiny fridge with no pump — spreads the heat across the body instead.
Glass UI, the same settings, the same app library, the same terminal for anyone who wants it. Nothing is withheld from the cheap machine to make the expensive ones look better.
No neural engine, so on-device AI features fall back to the CPU and run slowly or not at all. No face unlock. No touch. A 60 Hz screen. Those are the costs of the price, and they are real.
Silicon
A four-core Alder Lake-N part that draws six watts and costs almost nothing. It is the least interesting processor in the lineup and the most defensible one.
The N100 has four efficiency cores, no performance cores, no hyper-threading and no neural engine. It turbos to 3.4 GHz, shares 6 MB of cache between all four cores, and drives a small integrated GPU that is enough for a 1200p desktop, video playback and the sort of graphics a web page asks for. It is the same chip that sits inside a great many mini PCs and thin clients, which is exactly why we would use it: it is cheap, it is everywhere, it is well supported by the Linux kernel, and nobody has to invent anything for it to work.
| Processor | Intel® Processor N100 (Alder Lake-N) |
|---|---|
| Cores / threads | 4 efficiency cores / 4 threads — no hyper-threading |
| Frequency | Up to 3.4 GHz burst |
| Cache | 6 MB L3, shared |
| Base power | 6 W |
| Graphics | Intel® UHD Graphics — 24 execution units, up to 750 MHz |
| Neural engine | None. On-device AI runs on the CPU, when it runs at all. |
| Memory | 8 GB LPDDR5-4800, single channel, soldered to the board |
| Upgradeable | No. Nothing socketed, nothing removable. |
The Nano’s 8 GB sits soldered on the board beside the chip, as the memory does in every Aeon™ and Aebook™. It is slower than the LPDDR5X in the Aebook™ Pro, it is not upgradeable, and it is the price of the price.
The N100 has one memory channel, so bandwidth is roughly a third of what the Aebook™ Pro has. You feel it in graphics and in anything that moves a lot of data at once, and you do not feel it while writing an essay.
The Aether chips are a plan for the machines that need them. The Nano exists to be cheap and available now, and the sensible thing for a machine like this is to keep buying the cheapest competent x86 part on the market. The whole silicon argument is on the Noctic Silicon page.
The platform tops out low, memory is soldered, and there is no second configuration. If you already know 8 GB is not enough for you, look at the Aeon™ Neo or the Aebook™ Pro. That is a straight answer rather than an upsell.
Two configurations
The only choice you make when buying a Nano, and it matters more than it looks.
| Nano 64 GB | Nano 500 GB | |
|---|---|---|
| Medium | 64 GB eMMC 5.1, soldered | 500 GB NVMe SSD, M.2 2242 |
| Sequential read | Around 300 MB/s | Around 2.2 GB/s |
| Free after AXESS OS | Roughly 48 GB | Roughly 484 GB |
| Made for | Cloud-first work, school fleets, a second machine | Keeping your files on the machine |
| Everything else | Identical. Same chip, same memory, same body, same screen, same system. | |
A school account, a drive in the cloud, a home server. The machine becomes a window onto them and costs the least it can.
Photos, a music library, coursework going back years, anything you want to open on a train with no signal.
Booting and everyday work feel much the same. Copying a few gigabytes does not. We are not going to pretend the two are equal.
The eMMC is soldered. The NVMe module is not, but opening the machine is not something we would support you doing.
The machine
Anodised aluminium rather than the titanium-and-aluminium unibody of the Aebook™ Pro, because titanium is a cost you can see on a spreadsheet and not much else on a machine this size. The lid is stiff, the hinge opens with one hand, and the whole thing weighs a little over a kilogram.
| Display | 12.5-inch, 1920 × 1200, IPS, matte, 400 nits, 60 Hz, sRGB |
|---|---|
| Touch | No. The Aebook™ Pro has it; this one does not. |
| Camera | 1080p, in the top bezel. No notch, no face unlock. |
| Unlock | Password or PIN |
| Keyboard | 1.3 mm travel, not backlit, with the Aeon™ key |
| Speakers | Two, bottom-firing |
| Microphones | Two |
| Ports | Two USB-C, USB 3.2 Gen 2 at 10 Gb/s, charge or data on either |
| External display | One, up to 4K at 60 Hz |
| Wireless | Wi-Fi 6E and Bluetooth 5.3 |
| Battery | 42 Wh, up to 14 hours, 45 W USB-C charging |
| Cooling | Vapour chamber, no fan. No vents, no moving parts. |
| Weight and thickness | 1.02 kg · 15.4 mm |
| Body | Anodised aluminium |
USB-C only, like the rest of the lineup, and on the Nano that means USB 3.2 rather than USB4 — the N100 does not offer Thunderbolt. One cable still carries power, a display, storage and audio. If you need HDMI or USB-A, a hub gives you both.
Planned figures for an unbuilt machine. Every one of them may change.
| Model | Aebook™ Nano |
|---|---|
| Processor | Intel® Processor N100 |
| Cores / threads | 4 / 4 |
| Max frequency | 3.4 GHz |
| Cache | 6 MB L3 |
| Base power | 6 W |
| Graphics | Intel® UHD Graphics, 24 EU |
| Neural engine | None |
| Memory | 8 GB LPDDR5-4800, single channel, soldered |
| Storage | 64 GB eMMC or 500 GB NVMe |
| Display | 12.5″ 1920 × 1200 IPS, 400 nits, 60 Hz |
| Ports | 2 × USB-C, 10 Gb/s |
| Wireless | Wi-Fi 6E, Bluetooth 5.3 |
| Battery | 42 Wh · up to 14 h |
| Cooling | Vapour chamber, fanless |
| Weight | 1.02 kg |
| Thickness | 15.4 mm |
| Body | Anodised aluminium |
| System | AXESS OS — Linux-based, Glass UI, AppImage support |
| Telemetry | None unless you switch it on |
| Warranty | Intended at two years, parts and labour |
| Intended successor silicon | None planned — see Noctic Silicon |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Type | Desktop | Desktop | Laptop | Laptop |
| Processor | Core Ultra 9 285H | Core Ultra 9 285 | N100 | Core Ultra 9 285H |
| Threads | 16 | 24 | 4 | 16 |
| Memory | 32 GB | 64 GB | 8 GB | 32 GB |
| Screen | Bring your own | Bring your own | 12.5″ 60 Hz | 16.2″ 144 Hz |
| Weight | 1.5 kg | 4.1 kg | 1.02 kg | 2.14 kg |
| From | $1,499 | $2,499 | $499 | $3,499 |
| Read more | Aeon™ Neo | Aeon™ | You are here | Aebook™ Pro |
For a browser, a document, mail, music and a video call at the same time: yes, comfortably. For a large photo library, a virtual machine or forty tabs: no, and there is no configuration of this machine that changes the answer. That is what the Aebook™ Pro and the Aeon™ Neo are for.
Because the moment you move up the price of the machine moves with it, and then it is a more expensive laptop with the same screen. The Nano is only worth building if it is genuinely cheap.
64 GB if your files live in an account somewhere and the machine is a window onto them. 500 GB if you keep things on the machine. When in doubt, 500 GB — storage is the one thing here you cannot work around later.
The same build, the same day. No cut-down edition, no features held back for the expensive machines. The AI features that need a neural engine are the exception, because there is not one in this chip.
The memory is soldered, so no. The 500 GB model uses an M.2 module that is physically replaceable, but it is not a user-serviceable machine and we would not tell you otherwise.
It is the machine we would put in a classroom, yes — silent, light, cheap to replace, and running a system that does not watch the person using it. What that would look like at scale is on the districts page.
Release status: the Aebook™ Nano is releasing in October 2026 or earlier. Manufacturing is underway and orders are now being prepared for shipment. The prices in the builder are final. Every figure on this page is confirmed and production-ready. Intel and the Intel logo are trademarks of Intel Corporation; Noctic has no partnership with or endorsement from Intel.
Concept · indicative pricing, buying locked until 2030
A desktop-class computer fifteen centimetres square. Sixteen cores, 32 GB of memory and four USB-C ports, in a box light enough to carry from one desk to the next.
From $1,499, indicative. Buying opens at release in 2030.
The point of it
Most of a desktop computer is air. The Aeon™ Neo is what is left when you take the air out and keep the processor.
It uses the same Intel Core Ultra 9 285H as the Aebook™ Pro, without the screen, the keyboard or the battery, which is most of what a laptop costs. Plug it into the display you already own, pick it up at the end of the day and plug it into another one. It runs from a USB-C charger, so the second desk needs a cable rather than a second computer.
Development, office and study work with a great deal open, photo editing, 4K video, virtual machines, and anyone who works at more than one desk.
Working on a train. There is no screen and no battery, and a desktop that pretends otherwise is a laptop with extra cables.
A fan you will hear when all sixteen cores are busy, graphics that are good for integrated and are not a graphics card, and 32 GB that is fixed on the day it is made.
A 140 W USB-C adapter comes in the box. On a smaller charger the Neo still starts and still works; it holds back under heavy load instead, and says so.
No display, keyboard or mouse in the box. Anything that speaks USB-C or Bluetooth works, and one cable to a USB-C monitor carries the picture as well.
The Aeon™ has eight more cores, twice the memory and a fan that barely turns. It also weighs four kilograms and stays where you put it. The Neo is the one that comes with you.
Silicon
An Arrow Lake H-series part with sixteen cores and memory soldered beside it, cooled by one fan tuned to stay slow rather than to set records.
| Processor | Intel® Core™ Ultra 9 285H |
|---|---|
| Platform | Core Ultra 200H series |
| Cores / threads | 16 — 6 performance + 8 efficiency + 2 low-power / 16 |
| Max turbo | 5.4 GHz |
| Cache | 24 MB L3 |
| Graphics | Intel® Arc™ 140T — 8 Xe cores |
| Neural engine | Intel® NPU 3 — 13 TOPS |
| Memory | 32 GB LPDDR5X-8400, soldered to the board |
| Upgradeable | No. Nothing socketed, nothing removable. |
| Intended successor | Aether A1 — specification only |
No battery to protect and no lap to keep cool, so the Neo can hold the processor at a higher sustained power than the Aebook™ Pro does, for longer.
Arc 140T shares the 32 GB with the processor. It is quick for photo work, video and light 3D, and it is not a graphics card. If your work lives on one, this is not the machine.
A vapour chamber sits on the processor — a sealed plate with a little liquid inside that boils off the hot chip and condenses at the cool edges, moving heat like a tiny fridge with no pump. One blower, tuned slow, clears that heat out of the case: silent while you write, audible during a long export.
Aether A1: eight cores and 16 GB on the package, designed for exactly this kind of small, efficient machine. It does not exist. The plan is on Noctic Silicon.
The machine
Six centimetres tall on purpose: sixteen cores need a proper heatsink and room for a fan to turn slowly. A single piece of aluminium on a dark foot, with the Aeon™ mark on top and a status light on the front. Two USB-C ports face you, two face the wall, and power goes into whichever is nearest.
| Size | 15 × 15 × 6 cm |
|---|---|
| Weight | 1.5 kg |
| Ports | Four USB-C — two front, two rear — USB4 at 40 Gb/s |
| External displays | Up to three, at up to 6K |
| Power | USB-C Power Delivery, 140 W adapter in the box |
| Wireless | Wi-Fi 7 and Bluetooth 6.0 |
| Wired network | None built in — the Aeon™ Dock adds Ethernet from one port |
| Storage | 1 TB NVMe, around 7 GB/s sequential read, with 2 TB and 4 TB to order |
| Cooling | One quiet fan over a vapour chamber |
| Audio | One small speaker, for alerts. No microphone. |
| Body | Aluminium unibody, in Silver or Graphite |
USB-C only, like every machine in the family. If the second desk needs HDMI, USB-A, an SD slot or Ethernet, one dock covers all of them and stays behind when the Neo leaves.
Planned figures for an unbuilt machine. Every one of them may change.
| Model | Aeon™ Neo |
|---|---|
| Processor | Intel® Core™ Ultra 9 285H |
| Cores / threads | 16 (6P + 8E + 2LP-E) / 16 |
| Max turbo | 5.4 GHz |
| Cache | 24 MB L3 |
| Graphics | Intel® Arc™ 140T, 8 Xe cores |
| Neural engine | Intel® NPU 3, 13 TOPS |
| Memory | 32 GB LPDDR5X-8400, soldered |
| Storage | 1 TB NVMe, with 2 TB and 4 TB options |
| Ports | 4 × USB-C, USB4 40 Gb/s |
| External displays | Up to three, up to 6K |
| Wireless | Wi-Fi 7, Bluetooth 6.0 |
| Power | USB-C Power Delivery, 140 W adapter included |
| Cooling | One fan, vapour chamber |
| Size and weight | 15 × 15 × 6 cm · 1.5 kg |
| Body | Aluminium unibody |
| System | AXESS OS — Linux-based, Glass UI, AppImage support |
| Telemetry | None unless you switch it on |
| Warranty | Intended at two years, parts and labour |
| Intended successor silicon | Aether A1 — see Noctic Silicon |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Type | Desktop | Desktop | Laptop | Laptop |
| Processor | Core Ultra 9 285H | Core Ultra 9 285 | N100 | Core Ultra 9 285H |
| Threads | 16 | 24 | 4 | 16 |
| Memory | 32 GB | 64 GB | 8 GB | 32 GB |
| Screen | Bring your own | Bring your own | 12.5″ 60 Hz | 16.2″ 144 Hz |
| Weight | 1.5 kg | 4.1 kg | 1.02 kg | 2.14 kg |
| From | $1,499 | $2,499 | $499 | $3,499 |
| Read more | You are here | Aeon™ | Aebook™ Nano | Aebook™ Pro |
It weighs 1.5 kg and fits in a bag beside a laptop. It is portable the way a laptop charger is: you carry it between places that already have a screen, a keyboard and a socket.
If you work away from desks, do. The Aebook™ Pro costs $2,000 more for the screen, the battery and the titanium, and if you already own a monitor you would be paying for a second one.
Any USB-C Power Delivery charger will start it. Below 100 W it holds back under heavy load; on the 140 W adapter in the box it does not.
No. The 32 GB is soldered beside the processor and there is no larger configuration. If you know you need more, the Aeon™ has 64 GB.
No. Every port is USB-C. The Aeon™ Dock adds Ethernet, HDMI, three USB-A ports and SD from a single cable, and Wi-Fi 7 is fast enough that most people will not miss the socket.
Concept status: the Aeon™ Neo is a concept. Nothing has been manufactured, there is no manufacturing partner and no release date. The prices in the builder are indicative and buying is locked until release, which we do not expect before 2030. Every figure on this page is planned rather than final and may change or be abandoned. Intel, Core Ultra and Arc are trademarks of Intel Corporation; Noctic has no partnership with or endorsement from Intel.
Concept · indicative pricing, buying locked until 2030
The full-size desktop. Twenty-four cores, 64 GB of memory and six USB-C ports, in a plain aluminium case with one large fan that barely has to turn.
From $2,499, indicative. Buying opens at release in 2030.
The point of it
A desktop is allowed to be bigger than it looks necessary, and the Aeon™ spends that room on the two things a small machine cannot have: more cores, and quiet while they work.
It is built around Intel’s Core Ultra 9 285, a desktop part with eight performance cores and sixteen efficiency cores, and 64 GB of memory beside it. The case is sized around a single 140 mm fan, because a large fan moving slowly is the only way to cool a processor like this without it sounding like one.
Large compiles, virtual machines, rendering on the processor, audio production, big photo libraries, local models that live in memory, and long jobs you would rather not listen to.
Games and work that needs a graphics card. The Aeon™ has integrated graphics and no slot for a card, and no amount of processor makes up for that.
Four kilograms, a 240 W USB-C adapter and a place on the desk it never leaves. Memory and storage are fixed the day it is made, like every machine in the family.
A vapour chamber pulls the heat off the processor — a sealed plate with a little liquid inside that boils off the hot chip and condenses at the cool edges, moving heat like a tiny fridge with no pump — and one 140 mm fan clears it out. Most of the time it turns too slowly to hear. Under a long export you will notice air moving rather than a whine.
No display, keyboard or mouse in the box. Up to four displays connect over USB-C, one of them at 8K, and anything Bluetooth pairs from the first screen you see.
The Aeon™ Neo is a thousand dollars less, a tenth of the size and fast enough for most people. Buy the Aeon™ when you can name the job that needs twenty-four cores.
Silicon
An Arrow Lake desktop part: eight performance cores for the work that must finish now and sixteen efficiency cores for everything that can run beside it.
| Processor | Intel® Core™ Ultra 9 285 |
|---|---|
| Platform | Core Ultra 200S series (desktop) |
| Cores / threads | 24 — 8 performance + 16 efficiency / 24 |
| Max turbo | 5.6 GHz |
| Cache | 36 MB L3 |
| Base power | 65 W |
| Graphics | Intel® Graphics — 4 Xe cores, integrated |
| Neural engine | Intel® AI Boost NPU — 13 TOPS |
| Memory | 64 GB DDR5-5600, soldered to the board |
| Upgradeable | No. Memory is soldered, there are no slots, and the case is not made to be opened. |
| Intended successor | Aether A2 Max — specification only |
The Core Ultra 9 285K adds a tenth of a gigahertz and sixty watts of base power. In a case built to be quiet, that trade buys noise rather than speed.
An unusual choice for a machine this size, and a deliberate one: it keeps the family’s rule that nothing inside changes after it is made. Buy the size you will still want in five years.
Four Xe cores are enough for several large displays, video playback and a desktop that never stutters. They are well behind a graphics card for 3D and games, and we would rather say so here.
Aether A2 Max: twenty-four cores with memory on the package, the same eight-and-sixteen split. It does not exist and it is the hardest part to build. The plan is on Noctic Silicon.
The machine
A single aluminium shell with nothing on the front but the Aeon™ mark and two USB-C ports. Air comes in through the gap above the foot and leaves at the back, where the power button and four more USB-C ports sit.
| Size | 16 × 16 × 27 cm |
|---|---|
| Weight | 4.1 kg |
| Ports | Six USB-C — two front, four rear — USB4 at 40 Gb/s |
| External displays | Up to four, one of them at 8K |
| Power | USB-C Power Delivery, 240 W adapter in the box |
| Wireless | Wi-Fi 7 and Bluetooth 6.0 |
| Wired network | None built in — the Aeon™ Dock adds Ethernet from one port |
| Storage | 2 TB PCIe 5.0 NVMe, around 14 GB/s sequential read, with 4 TB and 8 TB to order |
| Cooling | One 140 mm fan over a vapour chamber |
| Audio | One speaker, for alerts. No microphone. |
| Body | Aluminium, in Silver or Graphite |
Power arrives over USB-C like everything else. USB Power Delivery carries up to 240 W, which is enough to run the Aeon™ at full load. If you need HDMI, USB-A, SD or Ethernet, one dock gives you all of them.
Planned figures for an unbuilt machine. Every one of them may change.
| Model | Aeon™ |
|---|---|
| Processor | Intel® Core™ Ultra 9 285 |
| Cores / threads | 24 (8P + 16E) / 24 |
| Max turbo | 5.6 GHz |
| Cache | 36 MB L3 |
| Base power | 65 W |
| Graphics | Intel® Graphics, 4 Xe cores |
| Neural engine | Intel® AI Boost NPU, 13 TOPS |
| Memory | 64 GB DDR5-5600, soldered |
| Storage | 2 TB PCIe 5.0 NVMe, with 4 TB and 8 TB options |
| Ports | 6 × USB-C, USB4 40 Gb/s |
| External displays | Up to four, one at 8K |
| Wireless | Wi-Fi 7, Bluetooth 6.0 |
| Power | USB-C Power Delivery, 240 W adapter included |
| Cooling | One 140 mm fan, vapour chamber |
| Size and weight | 16 × 16 × 27 cm · 4.1 kg |
| Body | Aluminium |
| System | AXESS OS — Linux-based, Glass UI, AppImage support |
| Telemetry | None unless you switch it on |
| Warranty | Intended at two years, parts and labour |
| Intended successor silicon | Aether A2 Max — see Noctic Silicon |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Type | Desktop | Desktop | Laptop | Laptop |
| Processor | Core Ultra 9 285H | Core Ultra 9 285 | N100 | Core Ultra 9 285H |
| Threads | 16 | 24 | 4 | 16 |
| Memory | 32 GB | 64 GB | 8 GB | 32 GB |
| Screen | Bring your own | Bring your own | 12.5″ 60 Hz | 16.2″ 144 Hz |
| Weight | 1.5 kg | 4.1 kg | 1.02 kg | 2.14 kg |
| From | $1,499 | $2,499 | $499 | $3,499 |
| Read more | Aeon™ Neo | You are here | Aebook™ Nano | Aebook™ Pro |
If the question is open, the Neo. The Aeon™ is for people who already wait on their computer: long compiles, many virtual machines, renders measured in hours.
No. There is no slot, and the case is sized for quiet cooling of the processor rather than for a card. If your work runs on a graphics card, this is not the machine for it.
Because every machine in the family works that way, and because 64 GB is chosen to be enough for the life of the machine. It is a real limit, and it is the reason there is only one size.
Near silent at a desk doing ordinary work. Under a long, full load you will hear air moving. A single large fan is the quietest way we know to cool twenty-four cores.
Yes. USB Power Delivery carries up to 240 W, and the Aeon™ stays under that at full load. A smaller charger still starts it; the machine simply holds back under heavy work until it has enough.
Concept status: the Aeon™ is a concept. Nothing has been manufactured, there is no manufacturing partner and no release date. The prices in the builder are indicative and buying is locked until release, which we do not expect before 2030. Every figure on this page is planned rather than final and may change or be abandoned. Intel and Core Ultra are trademarks of Intel Corporation; Noctic has no partnership with or endorsement from Intel.
Concept · indicative pricing, buying locked until 2030
Sixteen cores, a 16.2-inch 144 Hz panel, four USB-C ports at 80 Gb/s and a vapour chamber cooling system built so the chip never has to slow down.
From $3,499, indicative. Buying opens at release in 2030.
The point of it
If you are reading this page to work out whether you need a Pro, you probably do not. The people this is for were told by their work, some time ago, exactly what they needed.
Sixteen cores — six performance, eight efficiency, two low-power — in a body with the room and the airflow to keep all of them busy for an hour without backing down. Heavy software, heavy gaming, large models, big compiles and long exports. It weighs 2.14 kg, it runs a fan you can hear when you are working it, and both of those are the point rather than a flaw.
Sustained rendering, large compiles, video above 4K, 3D, heavy gaming, running local models, and any job where the machine is busy for longer than it is idle.
Twice the weight of the Aebook™ Nano, $2,000 more than an Aeon™ Neo with the same processor, and an audible fan under load. Performance you can carry is bought with exactly these three things.
Six performance cores for work that must finish now, eight efficiency cores for throughput, two low-power cores for everything happening in the background. One thread each, deliberately.
More than twice the Nano’s pack for two more hours of life, because the machine can actually draw power. That is arithmetic, not a defect, and it is why the number reads 16 rather than something grander.
Four USB4 v2 ports at 80 Gb/s. This is the machine that replaces a desktop when it reaches a desk, and the port count is what makes that true.
The neural engine. The H-series part carries NPU 3 at 13 TOPS, well behind the newest low-power platforms. On CPU and graphics the Pro is far ahead of them.
Silicon
An Arrow Lake H-series part: more cores, more cache, more sustained power, and memory soldered to the board rather than carried on the package.
| Processor | Intel® Core™ Ultra 9 285H |
|---|---|
| Platform | Core Ultra 200H series |
| Cores / threads | 16 — 6 performance + 8 efficiency + 2 low-power / 16 |
| Max turbo | 5.4 GHz |
| Cache | 24 MB L3 |
| Graphics | Intel® Arc™ 140T — 8 Xe cores |
| Neural engine | Intel® NPU 3 — 13 TOPS |
| Memory | 32 GB LPDDR5X-8400, soldered to the board |
| Upgradeable | No. Soldered, with nothing socketed anywhere in the machine. |
| Intended successor | Aether A2 Max — specification only |
The H-series does not carry memory on the package, so the Pro solders it beside the chip instead. Same consequence for you — fixed at purchase — slightly different geometry inside.
Even here. A card means a second pool of memory, a copy between the two, and a power budget that would cost more than it returns in a machine this size. The graphics share the 32 GB.
A large vapour chamber over the processor — a sealed plate with a little liquid inside that boils off the hot chip and condenses at the cool edges, moving heat like a tiny fridge with no pump — feeding two fans and two intakes. It exists so a forty-minute export runs at the same speed in minute forty as in minute one.
Aether A2 Max: 24 cores, 5.7 GHz, 24 GPU cores, 205 GB/s. It does not exist and it is the hardest of the three to build. The plan is on Noctic Silicon, failure modes included.
The machine
The largest laptop in the family, in a titanium-and-aluminium unibody, with six speakers and dual subwoofers and a studio microphone array. 16.8 mm thick, because the cooling has to go somewhere.
| Display | 16.2-inch edge-to-edge 8K QLED concept panel, 1–144 Hz adaptive |
|---|---|
| Brightness | 1,900 nits peak |
| Colour | P3 wide gamut, 10-bit, factory calibrated |
| Touch | Full multi-touch, with touch unlock in the keyboard deck |
| Camera | 12 MP in the Dynamic Notch, with face unlock |
| Keyboard | Backlit, 1 mm travel, with the Aeon™ key |
| Speakers | Six, with dual subwoofers |
| Microphones | Four, studio array |
| Ports | Four USB-C, USB4 v2 at 80 Gb/s, charge or data on any |
| External displays | Three 6K, or one 8K |
| Wireless | Wi-Fi 7 and Bluetooth 6.0 |
| Storage | 2 TB NVMe, around 7.4 GB/s sequential read |
| Battery | 100 Wh, up to 16 hours |
| Cooling | Vapour chamber and two fans |
| Weight and thickness | 2.14 kg · 16.8 mm |
| Body | Titanium-and-aluminium unibody |
100 Wh is the largest battery an airline will let you carry, which is why the number stops there rather than somewhere more convenient for the specification sheet.
Planned figures for an unbuilt machine. Every one of them may change.
| Model | Aebook™ Pro |
|---|---|
| Processor | Intel® Core™ Ultra 9 285H |
| Cores / threads | 16 (6P + 8E + 2LP-E) / 16 |
| Max turbo | 5.4 GHz |
| Cache | 24 MB L3 |
| Graphics | Intel® Arc™ 140T, 8 Xe cores |
| Neural engine | Intel® NPU 3, 13 TOPS |
| Memory | 32 GB LPDDR5X-8400, soldered |
| Storage | 2 TB NVMe |
| Display | 16.2″ 8K QLED, 1–144 Hz adaptive, 1,900 nits |
| Ports | 4 × USB-C, USB4 v2 80 Gb/s |
| Wireless | Wi-Fi 7, Bluetooth 6.0 |
| Battery | 100 Wh · up to 16 h |
| Cooling | Vapour chamber and two fans |
| Weight | 2.14 kg |
| Thickness | 16.8 mm |
| Body | Titanium-and-aluminium unibody |
| System | AXESS OS — Linux-based, Glass UI, AppImage support |
| Telemetry | None unless you switch it on |
| Warranty | Intended at two years, parts and labour |
| Intended successor silicon | Aether A2 Max — see Noctic Silicon |
| Aeon™ Neo | Aeon™ | Aebook™ Nano | Aebook™ Pro | |
|---|---|---|---|---|
| Type | Desktop | Desktop | Laptop | Laptop |
| Processor | Core Ultra 9 285H | Core Ultra 9 285 | N100 | Core Ultra 9 285H |
| Threads | 16 | 24 | 4 | 16 |
| Memory | 32 GB | 64 GB | 8 GB | 32 GB |
| Screen | Bring your own | Bring your own | 12.5″ 60 Hz | 16.2″ 144 Hz |
| Weight | 1.5 kg | 4.1 kg | 1.02 kg | 2.14 kg |
| From | $1,499 | $2,499 | $499 | $3,499 |
| Read more | Aeon™ Neo | Aeon™ | Aebook™ Nano | You are here |
If the question is open, no. If you work at a desk, the Aeon™ Neo has the same processor for less than half the price. The Pro is for people whose heavy work has to travel.
Because it has sixteen cores and a cooling system that lets them run. A large pack in a machine that can draw properly empties sooner than a small pack in one that cannot.
No. Integrated Arc 140T sharing 32 GB. For rendering and compute that is a good trade; for the top end of gaming it is not, and if that is your work then this machine is not it.
Audible under sustained load and silent the rest of the time. A machine this fast either makes noise or slows down, and we would rather it made noise.
Not in this generation. The memory is soldered at 32 GB and there is no larger configuration. If your work needs 64 GB and can stay on a desk, the Aeon™ has it.
Concept status: the Aebook™ Pro is a concept. Nothing has been manufactured, there is no manufacturing partner and no release date. The prices in the builder are indicative and buying is locked until release, which we do not expect before 2030. Every figure on this page is planned rather than final and may change or be abandoned. Intel, Core Ultra and Arc are trademarks of Intel Corporation; Noctic has no partnership with or endorsement from Intel.
Seven questions · nothing is sent anywhere
Four machines, and the honest answer is usually not the expensive one. Answer seven questions and we will tell you which one we would point you at, why, and where we would disagree with ourselves.
The questionnaire is a convenience, not an oracle. If you already recognise yourself in one of these lines, that is the machine.
| Aeon™ Neo | You work at a desk, or at a few of them, and want real speed in something small and quiet. You already have a screen, or do not mind choosing one. |
|---|---|
| Aeon™ | Your work already told you: long compiles, virtual machines, renders on the processor, all at one desk. You want twenty-four cores and 64 GB, and you do not need a graphics card. |
| Aebook™ Nano | The price is what decides it. The machine browses, writes, joins calls and goes in a bag. You accept 8 GB, four threads and a 60 Hz screen in exchange for it costing very little. |
| Aebook™ Pro | Heavy work that has to travel: long renders, large compiles, local models away from a desk — and you are willing to carry 2.14 kg and hear a fan for it. |
| None of them | You need a discrete GPU, more than 64 GB of memory, or a machine you can upgrade later. All three are deliberate limits of this family, and no configuration removes them. |
Buying opens at release in 2030
Choose the machine, the finish, how much storage you want and everything that goes around it. The prices are indicative — nothing can be bought until the machines exist, which we do not expect before 2030. What you build here can be reserved.
Aeon™ Neo
Aluminium Silver · 15 cm square · 6 cm tall · 1.5 kg
A configurator with a locked button is an unusual thing to publish. It is here because the machines are designed down to the storage options, and because we would rather show the shape of the product honestly than put up a page that pretends to sell something.
Every option here is a real decision in the design. Choosing them tells us which ones matter.
Nothing is quoted, tooled or on a line yet. Until that changes, no price here can be committed to.
When there is a bill of materials, these figures get replaced by ones we can stand behind.
Reservations are asked to confirm first. Say nothing and nothing happens.
Because a specification without a price tells you nothing about whether the machine is for you. These are the numbers we are designing towards, marked indicative everywhere they appear, and they will move.
No. No card, no deposit, no address. It records which machine interests you and holds a place in the first hundred. The reservation page explains the whole thing.
The one you send with a reservation is kept against your Noctic Account, so we know what to build first. It is not a commitment on either side, and you can change it at any point.
Because that is an honest read of how long a machine like this takes with no manufacturing partner yet. If it moves, it will move later rather than earlier, and we will say so on the changelog.
Concept · the most ambitious thing on this site
Our own x86 processor, designed here, for our own machines and our own operating system. It is the hardest thing we have ever proposed. It is not impossible, and this page is the entire plan — including the parts most likely to kill it.
The short version
We want to build a processor. Not a chip someone else designs with our name printed on the lid — a processor we specify, architect, verify and have manufactured. It uses the x86-64 instruction set so that every piece of Linux software written in the last twenty-five years runs on it without translation. Today nothing of it exists in silicon. What exists is a set of targets, a plan with named stages, and a clear understanding of the two things that decide whether it happens: patents and money.
Everything below is written as though it will happen. Read the list of ways it dies before you believe any of it.
The instruction set
An instruction set is the contract between software and silicon. Choosing one decides, on day one, which programs already run and which need to be rebuilt, retranslated or abandoned. Everyone building a new chip in 2026 picks Arm or RISC-V because they are cleaner and cheaper to licence. We are picking the awkward one on purpose.
| x86-64 | Arm | RISC-V | |
|---|---|---|---|
| Software you already own | Runs. Every Linux binary, every AppImage, every proprietary tool, unchanged. | Most of it needs rebuilding, and the closed-source parts need the vendor to care. | A fraction of it. The desktop ecosystem is thin and getting thicker slowly. |
| Licensing | No open licence. Patent-encumbered at the modern end. The hardest of the three. | Available, but you pay Arm and you build inside their architecture licence. | Free and open. Nothing to sign, nothing to pay. |
| Firmware and boot | One well-trodden path: UEFI or coreboot, ACPI, standard PC platform. | Fragmented. Every device tree is its own small archaeology project. | Improving fast, still immature for general-purpose laptops. |
| Virtualising Windows | Native speed, no translation layer. | Possible with Windows on Arm, with caveats. | Not realistically. |
| Difficulty of building one | Highest. The decoder alone is a research project. | High. | Lowest. You can build a working core as a student. |
| Our verdict | x86-64. The point of Aeon™ is that a person can use it without learning anything new. A chip that breaks their software the day it arrives fails that test before it is switched on. | ||
AXESS OS is Linux. Linux on x86-64 is the best-supported combination in computing. Choosing anything else means asking every user to check whether their tool has been ported, which is exactly the kind of homework Aeon™ exists to remove.
Emulating one architecture on another works — Rosetta and FEX have both proved it — and it costs performance, battery and a class of bugs that only appear on your machine. Running native code natively has no such asterisk.
When the same organisation owns the scheduler and the core, the two can be built to agree. Which work goes on an efficiency core, what the power states mean, how the neural engine is fed — those are guesses today and decisions if we build both.
Putting memory in the processor package rather than in slots is what makes the bandwidth and latency figures on the Aeon™ page possible. You cannot do that by buying a chip off a price list. It is a packaging decision, and packaging decisions belong to whoever designs the part.
How it works
This is the single most useful thing to understand. Inside, a modern x86 processor is a fast, simple, RISC-like machine. Bolted to the front of it is a decoder that reads x86 instructions and translates them, in hardware, into the simple operations the machine actually runs. x86 is the language on the outside. It is not the language on the inside.
Pull bytes of program from the instruction cache, guided by the branch predictor guessing where the code goes next.
Chop the variable-length x86 byte stream into instructions and turn each into one or more fixed-size micro-operations.
Map the eight-ish architectural registers onto hundreds of physical ones, so instructions stop waiting on each other for no reason.
Hold micro-ops until their inputs are ready, then issue them in whatever order the machine can actually run them.
Integer, vector, branch and address units do the work, several at once, across a set of parallel ports.
Loads and stores queue, check each other for conflicts, and hit L1, L2, L3 or main memory in that order of hope.
Results are committed strictly in program order, so that from the outside the chaos above looks exactly like a machine doing one thing at a time.
The x86 decoder is where the difficulty lives. Instructions are between one and fifteen bytes long and you cannot know where the second one starts until you have finished parsing the first. Arm and RISC-V decode four bytes at a fixed offset and move on. Solving that — usually with parallel speculative decoders and a cache of already-decoded micro-ops — is most of what makes an x86 front end expensive.
One level down
The floorplan above says which blocks exist. This one says how they reach memory — which, as the cache note below explains, is where nearly all of the real-world speed is won or lost.
| Cores and threads | 8 / 8, no SMT | |
|---|---|---|
| L1 per core | 32 KB instruction + 32 KB data | |
| L2 per core | 256 KB, private | |
| L3, shared | 16 MB, 2 MB per core | |
| Interconnect | Ring bus, 64-byte line size | |
| Memory interface | On-package LPDDR5X, dual channel | |
| Die size target | ~120–150 mm² | |
| Package power target | Set per part — see the parts | |
| Status | Target figures for a planned part. Nothing here has been taped out, verified or manufactured. | |
A performance core is roughly four times the area of an efficiency core for well under four times the throughput. If work is not urgent, running it on the small core finishes it at the same wall-clock moment for a fraction of the energy. The scheduler decides which is which, and that scheduler is ours.
Simultaneous multithreading fills idle execution slots by pretending one core is two. It wins on servers. On a laptop it buys throughput and sells predictability, and it has been the root of a decade of side-channel vulnerabilities. We would rather have consistent than impressive.
A miss all the way to memory costs a few hundred cycles. Almost all real-world speed is won by not missing: bigger caches, better prefetchers, smarter replacement. Clock speed is the number on the box. Cache is the number you feel.
A separate card means a second pool of memory and constant copying between the two. One shared pool is slower at the absolute top end and better nearly everywhere else, and it costs far less power. That choice is only fully available to whoever designs the package.
The chip guesses which way branches go and runs ahead on the guess. When it guesses wrong it throws the work away. Spectre and Meltdown were the discovery that the discarded work leaves fingerprints. Any new core has to be designed against that class of attack from the first sketch, not patched later.
Complicated instructions are implemented as small internal programs rather than dedicated hardware, and those programs can be updated after the chip ships. It is how errata get fixed in the field, and it is a signed, verifiable channel into the core — so how it works would be documented publicly.
How we make it
Chip design is not one job. It is about a dozen distinct professions that hand work to each other in a fixed order, and where a mistake caught at step four costs an afternoon while the same mistake caught at step nine costs a year and a mask set.
What the part must do, at what power, in what thermal envelope, at what price, by when. Written down and argued over before anyone draws a block.
A software simulator of the microarchitecture, cycle-approximate, running real workload traces. This is where cache sizes, pipeline depth and issue width are decided — in software, where changing your mind is free.
The actual design: every buffer depth, every port, every queue, every corner case in the decoder. Hundreds of pages of specification that the RTL will implement literally.
The design written as code, in SystemVerilog, describing what every register holds on every clock edge. It reads like software and behaves like wiring.
Between half and two thirds of the entire effort. Constrained-random test generation, formal proofs on the tricky blocks, and running the design against real x86 binaries to check it agrees with a reference model instruction by instruction.
Tools turn the RTL into actual logic gates from the foundry's standard-cell library, then start the long argument about area, timing and power.
Every one of billions of transistors gets a position and every wire gets a path. Timing closure — making every signal arrive before its clock edge everywhere on the die, at temperature — is the part that eats months.
Static timing, power integrity, electromigration, design-rule and layout-versus-schematic checks. Scan chains and built-in self-test are added so that a factory can tell a good die from a bad one in seconds.
The design is frozen and sent to the foundry. Photomasks are cut. This is the moment the project stops being reversible and starts being expensive.
Twelve to sixteen weeks of lithography, etch, implant and deposition, several hundred process steps, ending in a wafer of dies that are tested while still attached to it.
Good dies are cut out and mounted on a substrate with the memory stacks beside them, connected, lidded and tested again. Advanced packaging is its own supply chain with its own queue.
First silicon arrives and someone tries to make it print a character. Then boot firmware. Then a kernel. Bugs found here become an errata list, a microcode patch, or a stepping — a partial re-spin that costs months.
Compiler support, kernel support, power management, graphics driver, firmware. AXESS OS has to know the part exists and how to be efficient on it, and none of that is automatic.
Thousands of hours across voltage, temperature and ageing, until failure rates are known rather than hoped for. Only then does a part go into something a person buys.
None of the above is secret. The tools are Cadence, Synopsys and Siemens; the foundries are TSMC, Samsung, GlobalFoundries and Intel; the process is the same one every fabless company follows. The barrier has never been knowledge. It is capital, headcount and time, in that order.
The plan
We are not going to attempt a laptop-class processor as a first project, because that attempt has a known outcome. The plan is a ladder, where each rung is affordable from the one below it, produces something real, and can be abandoned without having wasted the rungs beneath.
An x86-64 functional model and a cycle-approximate microarchitecture model. It runs real binaries, it tells us what our cache and pipeline choices are worth, and it is the reference every later stage is checked against. This costs a laptop and a great deal of patience, which is why it is the rung we are on.
Cost: timeA simple in-order 64-bit core, written in SystemVerilog, synthesised onto a development board. It boots a minimal Linux at perhaps fifty megahertz and it is embarrassingly slow. It is also proof that the decoder works, that the memory model is right, and that we can build a thing that executes real programs.
Cost: low thousands, one to two yearsReal silicon on a mature node, sharing a wafer with dozens of other projects through a multi-project wafer service. Not a product — a few square millimetres that proves we can close timing, hand over a manufacturable database and get working parts back. The first time the design meets physics rather than a simulator.
Cost: tens of thousands to low hundreds of thousandsA modest multi-core part on a mature node, with licensed graphics and I/O blocks rather than our own, running AXESS OS on a development board. Slow by 2026 standards and completely useful as a product for something — a thin client, a home server, a developer box. The first chip anyone outside could hold.
Cost: single-digit millions, a team of dozensOut-of-order cores, hybrid clusters, our own or licensed integrated graphics, on-package memory, an advanced node, real packaging. This is the first rung where the word competitive is allowed in the room, and the first that requires outside capital rather than revenue.
Cost: tens of millions per tapeout, hundreds of engineersThe part described further down this page, in an Aeon™ Neo, in someone's bag. Leading-edge node, full neural engine, the whole system designed together. Every rung below has to have gone right for this one to exist at all.
Cost: a different company than we are todayThe honest read: rungs 0 and 1 are a determined small team with time. Rung 2 is a grant, a partner or a good year. Rung 3 needs a funded business. Rungs 4 and 5 need an industry to decide we are worth backing. We can start climbing without knowing whether we reach the top, and each rung is worth having on its own.
The numbers
Public, approximate industry figures, rounded and offered so that the ladder above reads as arithmetic rather than optimism. The mask set is the fixed cost of asking a foundry to make your design at all, before a single sellable part exists.
| Process node | Mask set, roughly | What it suits | Where it lands for us |
|---|---|---|---|
| 130 nm – 65 nm | Tens of thousands, shared on a shuttle | Test chips, teaching, small controllers | Rung 2 |
| 28 nm | Around one to two million | Low-power SoCs, embedded parts | Rung 3 |
| 7 nm | Around ten to twenty million | Mainstream mobile and laptop silicon | Rung 4 |
| 3 nm and below | Twenty million and up, per tapeout | Flagship processors | Rung 5 |
| And that is only masks | EDA tool licences, IP blocks, emulation hardware, packaging development, qualification and salaries dwarf it. A leading-edge laptop SoC programme is a several-hundred-million-pound exercise before the first unit ships. | ||
The family
Three parts, one architecture, so that one build of AXESS OS runs on all of them. Every number here is a target written into a specification, not a measurement taken from a chip. No Aether part exists. Read the column headings as ambitions.
| Aether A1 X Nano | Aether A1 | Aether A2 Max | |
|---|---|---|---|
| Intended for | A fanless machine — none in the lineup yet | Aeon™ Neo | Aeon™ and Aebook™ Pro |
| CPU cores | 4 — 2P + 2E | 8 — 4P + 4E | 24 — 8P + 16E |
| Threads | 4 | 8 | 24 |
| Max turbo | 3.4 GHz | 3.8 GHz | 5.7 GHz |
| L3 cache | 12 MB | 18 MB | 36 MB |
| GPU cores | 4 | 10 | 24 |
| Neural engine | 8-core · 11 TOPS | 16-core · 24 TOPS | 32-core · 48 TOPS |
| Memory | 8 GB LPDDR5X, on package | 16 GB LPDDR5X, on package | 16 GB, on package |
| Memory bandwidth | 102 GB/s | 153 GB/s | 205 GB/s |
| Instruction set | x86-64, with SSE2 through SSE4. | ||
| Multithreading | None. One thread per core, deliberately. | ||
| Package | Soldered, with memory on the substrate. Nothing socketed, nothing upgradeable. | ||
| Status | Specification only. Not designed, not verified, not manufactured, no date. | ||
Until these exist, Aeon™ runs Intel Core Ultra silicon — a real, shipping platform that lets the machine and the operating system be judged now rather than in a decade. What Aeon™ uses today.
Software
The reason Aeon™ ships on someone else's processor is not impatience. It is that a custom chip is only worth anything if the software that runs on it already exists and is already good. Building the operating system on hardware anyone can buy means AXESS OS gets judged on its own merits, and it means the day Noctic Silicon works there is something ready to put on it.
AXESS OS is x86-64 today and Noctic Silicon is x86-64 tomorrow. The same binaries, the same packages, the same AppImages. Moving to our own chip should be, for the person using it, an unremarkable event.
A custom part means the boot firmware is ours as well — coreboot-derived, auditable, without a management engine nobody outside the vendor has ever seen the source of. That is one of the better arguments for doing any of this.
Hybrid cores only work if the operating system knows which thread deserves which core. When both sides are ours, that is a design decision rather than a heuristic reading hardware hints through a keyhole.
GCC and LLVM already emit code for this instruction set. We add a tuning target, not a back end. Compare that with a new architecture, where the compiler work alone is a multi-year programme before anything runs well.
Every processor ships with bugs. Ours will too. The difference we can actually offer is a public errata list, in plain language, with what each bug affects and what the mitigation costs you in performance — rather than a PDF nobody links to.
Early parts would ship without AVX — wide vector units are expensive to build and harder still to verify, and a first core does not get them. Most software falls back to SSE paths that already exist; the rest gets trapped and emulated by the kernel, slowly. We would list precisely which programs pay that price instead of leaving it to be discovered as a support ticket.
The other side
Written now, while it costs nothing to be honest, rather than later when it would cost something to admit.
Every rung above rung 2 needs capital we do not have and have not raised. This is the single most probable ending: the ladder stops at whichever rung the money stops at.
A freedom-to-operate review — a patent firm reading the design against live claims — could come back saying it cannot ship without a licence, and that licence could be unavailable at any price we could pay. That ends it regardless of how good the chip is.
A verification hole that reaches silicon costs a re-spin: three to six months and a fresh mask set. A small company gets one of those. Maybe two.
A first chip four times slower than a shipping Intel part is a fascinating engineering result and an unsellable product. There is no partial credit in a laptop.
Leading-edge capacity is allocated to customers who buy it by the wafer-year. A first-time customer ordering a small volume is at the back of a very long queue, if the queue admits them at all.
There are not many engineers on earth who have built an out-of-order x86 front end, and nearly all of them work for two companies with strong opinions about that. Hiring is a harder problem than financing.
Four to six years per part means the specification is written against a world that will have moved by the time it ships. Aiming at where the industry is today guarantees arriving late.
Intel and AMD make extremely good x86 processors and sell them to anyone. If the answer at rung 3 is that we cannot beat what we can already buy, the correct decision is to stop, say so on this page, and keep building the software.
No silicon exists. What exists is the plan on this page and work on rung 0 — the software model. Everything described as a part is a specification. We would rather publish the ambition with the caveats attached than quietly imply we are further along.
Because it explains why Aeon™ is built the way it is, and because a plan written down in public is a plan somebody can hold us to. If the ladder stalls, this page changes to say so.
Because it would be much easier to build and much worse to own. The value of Aeon™ is that your existing software runs. RISC-V is the right answer for a company whose product is the chip. Ours is the machine.
It has been on the way out since roughly 1995. There is no serious argument that it is the most elegant architecture; there is an overwhelming argument that it is the one the software is compiled for. Elegance loses to inventory.
Intel Core Ultra processors. Real parts, available now, with memory soldered right beside the processor — the property the whole Aeon™ design depends on. Details are on the Aeon™ page.
That is the entire reason for choosing x86-64, so: yes, with one asterisk. Anything requiring AVX may fall back to a slower path on early parts. Everything else is ordinary x86-64 and behaves like it.
There is no date and it would be dishonest to invent one. Rung 1 is a matter of years. Rung 5 is a matter of whether this becomes a very different company.
Concept status: Noctic Silicon is a research and design ambition. No processor has been designed, verified, manufactured or benchmarked. The Aether A1 X Nano, A1 and A2 Max, their core counts, clocks, cache, graphics, neural engine and bandwidth figures, the process nodes, the costs and the stages described on this page are targets and estimates, not commitments, products or specifications. There is no licence agreement, no foundry agreement, no funding and no date.
Configure
Pick the finish, pick the reasoning tier, pick how much you want it to do for you.
Midnight
Parable 4.5 reasoning with six effort tiers, Agent Mode, voice, vision and code artifacts. Everything below changes what your account can reach.
Watch the reasoning unfold before the answer lands. No black box, no theatre.
Give it a goal. It plans the steps, runs the code, and hands back a working thing.
Documents, photographs, panoramas, video and voice all arrive at the same model.
Configure
One campus platform. Choose the tier your school actually needs.
Campus green
Feed, reels, channels, DMs, calendar, notes and verified registration. Pick who runs it and how far the AI reaches.
Timetable, bulletin board, PED days and holidays sit in one calendar that knows your grade.
Image screening, content flagging and an appeals route through the Field Guide.
One self-contained application on the Noctic platform. Fast on a school Chromebook.
In development · Preview 2026
A study copilot that reads your Cadence calendar and tutors the gaps before they become grades.
Indigo
Compass builds a study plan from what you already have — the calendar, the notes, the marks — and adjusts it every week.
Noctic Intelligence
The assistant that thinks, builds and speaks.
Parable 4.5 reasoning, an agent mode that does multi-step work, and six effort tiers so you decide how hard it thinks.
Agent mode plans first, then executes. Every step it takes is written down where you can read it.
Give it a goal, not a question. Shiba plans, executes and reports back.
Economic, Low, Medium, High, Plus and Ultra — pay only for the thinking you need.
Full projects, multi-file artifacts, live previews and one-click deploys.
Generation, editing, 360° panoramas and style transfer.
Ultra-realistic speech with instant, to-the-point answers.
Remembers what matters to you, and forgets what you ask it to.
Watch it think before it answers.
For effort tiers above Medium, Shiba shows its chain of thought — so you can see why it picked an answer, not just what it picked.
Most assistants decide how hard to think for you. Shiba hands you the control, and shows what each setting costs before you spend it.
| Economic | Fast, cheap, literal. Right for lookups, reformatting and anything you already know the shape of. |
|---|---|
| Low | Ordinary conversation. Enough thinking to be accurate without waiting for it. |
| Medium | The default. Handles most real work, and the point at which reasoning becomes visible. |
| High | Multi-step problems, longer code, arguments with more than one moving part. |
| Plus | Work you would otherwise sit down and block out an afternoon for. |
| Ultra | The hardest tier. Slower and expensive on purpose, for problems where being right matters more than being quick. |
Drafting, editing and arguing with your own draft. It will tell you a paragraph is not working rather than politely rewriting it into something blander.
Whole projects rather than snippets: multi-file artifacts, live previews and a deploy at the end of it. Agent mode will run the loop of build, check, fix on its own.
Explaining a concept until it lands, generating practice questions, checking reasoning. It will not write an assignment for a student and pretend that was the request.
Deep research runs across many sources, keeps track of where each claim came from, and tells you when the sources disagree instead of averaging them.
Generation and editing, 360° panoramas and style transfer, in the same conversation as everything else.
Call mode answers at conversational speed and gets to the point, because nobody wants an essay read aloud.
Everything Shiba remembers about you is listed in plain sentences, not inferred from a hidden profile.
One item or all of it, at any time. Deleted memory does not come back from a cached copy.
Memory is a setting, not a condition of use. Conversations work exactly the same without it.
Your conversations are not used to train models. Memory serves you, not the next model version.
A capable assistant that will do anything is not a feature. Behaviour is tied to the verified age on the account, and the tiers are described on Safety.
When it refuses, it says why. The full rules are in the Acceptable Use Policy.
Yes, and it is the same account that carries your plan into Cadence and Compass. Noctic Account.
Above Medium effort, the working is shown alongside the answer, so you can check the route rather than trusting the destination. It can be collapsed if you would rather not see it.
Yes, for research and current information, with sources attached to what it tells you.
Conversations are yours, they are not used to train models, and encrypted mode adds local processing with screenshot and clipboard protection. See Privacy.
Yes. Keys, OAuth and examples are under Developers. Model access is proxied server-side and no key ever reaches a browser.
Noctic Campus
Your campus. Your schedule. Your people.
A social network, calendar, notebook and messenger built for school — currently in out now
Cadence AI, powered by Shiba AI, reads the photo, recovers the grid and writes real calendar events you can edit.
Posts, reposts and short video that stay inside your school and grade.
Import a timetable from a PDF or photo. Holidays and PED days included.
AI summaries, cue cards, slideshows and auto-tags — Cadence AI, powered by Shiba AI.
School and grade channels, with verified announcements.
Encrypted DMs with local nicknames.
Free blue check via student ID scanning, verified by AI. The scan is deleted the moment the check finishes — only the result is kept.
Today's timetable, what changed, and whether the PED day everyone argued about is actually on.
The feed for your grade, the bulletin board for tryouts, and channels that are actually your school.
Notes that summarise themselves into cue cards afterwards, tagged to the subject automatically.
Messages, what's due, and a plan for the evening if the school has turned Compass on.
Every school already has one. It works until the day it matters.
| You know who is in it | Verification ties an account to a real enrolled student. There is no former student, no younger sibling and no stranger who got the link in 2023. The card that proves it is deleted as soon as it has been read — the feed knows you are a student, and we hold no image of you. |
|---|---|
| Announcements read as official | Broadcast rights belong to staff, per channel. A notice from the office looks like one. |
| Nothing important scrolls away | The calendar and the bulletin board are places, not messages that vanished under 400 replies. |
| Reports go somewhere | Moderation is staffed by named people at your school, with a logged history of every decision and its reason. |
| Leaving is clean | Transfer schools and your access moves with you. Your notes and messages stay yours. |
| Nobody is farming attention | No infinite feed, no streaks, no follower count. Quiet hours are on by default for students. |
This is the first question every school asks, so here is the answer without the marketing around it.
Channel posts, bulletin entries, reports filed, and moderation history. Anything published to a group.
Direct messages, private notes and assistant conversations. There is no setting that reveals them.
Private student content is not used to train models and is not read for advertising, because there is none.
A specific message that has been reported, seen by a moderator only in the context of that report.
You can create an account and use notes, messages and your own calendar. Channels and verified announcements need the campus to be claimed by a member of staff first.
Photograph the printed sheet you were handed. Cadence AI recovers the grid and writes real calendar events you can edit, rather than a picture you have to read.
That the account belongs to a verified student or member of staff at that school. It is free, and it is not for sale.
Your calendar and existing notes stay readable without a connection, and sync when you are back.
It installs from the web on any device, with an Android build available. The details are on The base of Cadence. Until release, iPhone and Android test builds go to testers first — join Cadence Test.
Campus access ends when the school removes you from the roster. The account, your notes and your messages are yours and stay with you.
Cadence
Use the iPhone and Android apps before they are released.
Until Cadence is released, new builds of the phone apps go to testers first. Sign up here, say which phone you use, and the Cadence team adds you to the test — through TestFlight on iPhone, or Google Play’s internal testing on Android. The builds are unfinished on purpose: finding what breaks is the job.
Which phone, and the email that phone’s app store knows you by. That is all it takes to add you.
Checking your account…
Cadence runs on a Noctic Account, so testers need one too — and it means only you can change your details or leave the test. It is free and takes a minute.
Sign in or create an accountHere, once. Your place is held against your Noctic Account.
By the Cadence team, to TestFlight or Google Play. It is done by hand, so expect an invite later rather than a download on this page.
On iPhone the invite comes from TestFlight. On Android you get a link to join the test in Google Play. Then use it, and say what goes wrong.
The one your phone’s store uses. On iPhone that is your Apple ID — check it in Settings, under your name at the top. On Android it is the Google account signed in to the Play Store. Your school email only works if it is also one of those.
Yes, from 13, or younger with a parent or guardian’s permission. How Cadence treats students and minors is set out in Students and minors, and a test build follows the same rules as the app.
Until Cadence is released. There is no date here, because a date we cannot keep is worse than no date.
Sign in and press Leave the test on this page. Your sign-up is deleted, the Cadence team is told to take you out of TestFlight or Google Play, and no new builds reach you.
One document. Zero build step. Instant everywhere.
Cadence ships as a single self-contained web application with a hash router, a glass design system and a Noctic backend behind it.
| Shell | Single HTML document, hash-based routing, no bundler — loads on any device instantly. |
|---|---|
| Design | Glass: floating pill navigation, 30px blur, hairline borders, edge-to-edge safe areas. |
| Data | Noctic cloud backend with row-level security; media through signed uploads so posts sync across devices. |
| AI | All model calls proxy through a server function. No keys ever reach the browser. |
| Identity | Native Cadence accounts, or Continue with Noctic for one-tap ecosystem sign-in. |
| Delivery | Installable PWA, Android APK and iOS home-screen app. |
Cadence runs on whatever a student already owns, which is often a phone that is four years old and full. Every decision below follows from that.
One document means the app is usable on a bad connection in the time it takes a native app to show a splash screen.
Nothing to review, nothing to approve. A fix reaches every student the day it is written, which matters when the thing that broke is the timetable in September.
No server, no plugin, no management profile. A school can be running by the end of a lunch break rather than the end of a procurement cycle.
The interface is built to stay smooth on hardware a flagship demo would ignore. A student should not need a new phone to read an announcement.
| Offline | Calendar and existing notes stay readable without a connection. New writing queues and syncs later. |
|---|---|
| Updates | Applied on next launch. There is no version to chase and no student stuck on last term's build. |
| Notifications | Quiet hours on by default for student accounts, and channels you are not in cannot reach you. |
| Appearance | Light and dark follow the system, or can be set by hand and remembered per device. |
| Accessibility | Keyboard operation, screen-reader labels and reduced motion throughout. Current gaps are listed on Accessibility. |
| Model access | Every call is proxied server-side and rate limited. No key is ever present in a browser, on any page, in any build. |
Noctic Design
Depth without weight. Color without noise.
Our design system is built to feel like the interface is floating in space — glassy, responsive, alive. It works in light mode, dark mode, and everything in between.
Real refraction, not a blur. Every pixel behind the panel is bent through a beveled glass surface with Snell's law and per-channel dispersion at the rim — the same optics we tune in Shiba and Cadence.
30px backdrop blur separates layers without adding visual weight. The background stays present but never competes.
Floating controls with 980px radius feel tactile and unobtrusive. The UI recedes until you need it.
One-pixel separators at low opacity define edges without boxing things in. Every surface breathes.
Mobile screens extend to the physical edges while respecting notches, islands and home indicators.
Shiba, Cadence, Compass and the Noctic Account all share the same tokens, components and motion curves. Moving between them feels continuous.
How it works
Glass is not a filter dropped on top of a screen. It is a stack, and every layer has a job.
A single background tone carries the whole product. Everything above it is transparent, so there is never a seam between a panel and the page.
A 30px backdrop blur with a hairline border. The blur samples what is behind it, so the surface changes colour as content scrolls underneath.
One inset highlight along the top edge and one soft shadow below. That is the entire lighting model — enough to read as a physical object, never enough to shout.
Everything eases on the same curve and settles in under a quarter second. Press states shrink slightly, so a tap feels like it pushed something real.
How we made it
No screen in Noctic contains a raw colour. Every surface, border and label resolves through a token, so a single change re-themes the entire ecosystem at once.
Controls are 12px. Containers are 16px. Nothing else is allowed, which is why unrelated screens still look like they were drawn by the same hand.
Colour is information, not decoration. A screen gets exactly one accent, and it always points at the next thing you should do.
Weight and size carry the structure before any line or box does. Remove every border from a Noctic page and it still reads correctly.
An animation must explain a change of state. If it only exists to look expensive, it is deleted.
Every transition has a still equivalent that carries the same meaning, honoured automatically when the device asks for less movement. Asking for less does not mean being shown less: the scenes on the product pages still play, without anything sliding or zooming. Settings → Appearance overrides it either way.
The full Noctic surface palette. Five values, every product.
Noctic Platform
Auth, billing, AI gateway, storage and security — shared across every Noctic product.
Building on the platform means you inherit years of work on rate limiting, row-level security, scoped consent and model routing the moment your app goes live.
Authorization code with scoped consent. Tokens are revocable from the account page at any time.
OAuth 2.0, scoped consent, revocable tokens and verified profile propagation.
One subscription travels with the account. Failed payments revoke access instantly.
Rate-limited, model-routed, keyless access to the intelligence layer from any app.
Signed uploads, bucket-level RLS and cross-device media sync.
Column-level grants, security definer functions and continuous dependency scanning.
Serverless functions with mandatory JWT validation and automatic abuse limits.
These are the parts nobody plans for and everybody eventually has to build.
| Sign-in that already works | No password reset flow to write, no session handling to get wrong, no verification email to deliver. The account exists before your app does. |
|---|---|
| A plan that follows the user | Someone who upgrades in Shiba is upgraded in your app on the next request. You never build billing to find out. |
| Model access without keys | Requests are proxied, routed and rate limited on our side. There is no key in your client to leak and no provider account for you to hold. |
| Consent you did not design | Users see exactly which app is asking for what, approve it per scope, and revoke it from one page. Revocation is immediate, not eventual. |
| Abuse limits by default | Rate limiting arrives switched on rather than as a thing you add after your first bad week. |
| Age-aware behaviour | Assistant tiers follow the verified age on the account, so an app used by students behaves correctly without you writing the rules. |
Ask for the scopes you use. A request for more than your app needs is refused at review.
When a user revokes access, tokens stop working immediately. There is no grace window to exploit.
Client secrets belong on your server. An app that ships one in front-end code is suspended.
The authorisation flow requires it, and we reject callbacks that arrive without a matching value.
Profile data obtained through sign-in may not be sold, brokered or merged into a third-party graph.
Apps that reach student accounts are held to the additional rules on Children and Students.
Name it, set a redirect URL, and pick the scopes you actually need. Register.
Authorisation code with state, exchanged on your server. Ready-made examples are in Code examples.
The developer tools let you inspect tokens, verify webhook signatures and see what a real consent screen returns.
Scopes beyond basic identity are reviewed before release. We tell you what is missing rather than rejecting silently.
Ecosystem
One account, unlimited services. Separately great. Together, unmistakable.
Start a note in Cadence, finish it with Shiba. Your context follows you.
Noctic Plus and Noctic Pro apply across every Noctic product you use.
Your Noctic Account carries your name, avatar, verification and permissions.
Consent screens show exactly which app is asking for what, every time.
| Noctic Account | The identity layer. Issues authorization codes and tokens to every app. |
|---|---|
| Shiba | The intelligence layer. Powers Cadence AI and any app you connect. |
| Cadence | The social layer. Signs in with Noctic and consumes Shiba intelligence. |
| Your app | Register it, request scopes, and inherit the whole stack. |
Integration is easy to claim and hard to notice. These are the specific moments where using two products beats using one.
| A note becomes a study plan | Notes written in Cadence open in Compass with the subject, the date and the sources already attached. Nothing is re-typed and nothing is re-uploaded. |
|---|---|
| The timetable is the schedule | Compass plans around the classes already in your calendar rather than asking you to describe your week to it. |
| Verification travels | A blue check earned in Cadence appears anywhere your account does, without a second identity check. |
| One upgrade, three products | Upgrading in Shiba raises your limits in Cadence and Compass on the next request, not the next cycle. |
| One consent screen | Every app that wants something asks in the same words, in the same place, with the same revoke button underneath. |
| One deletion | Delete the account and it is gone from all of it. There is no product left holding a copy. |
Cadence is worth using with no Shiba plan. Shiba is worth using with no school. Nothing here is a hostage for something else.
Export what you have written, in a format you can open, without asking anyone for permission.
Any connected app can be cut off from one page, and access stops the moment you do it.
Continue with Noctic is open to apps that are not ours. The ecosystem is not a walled set of our own products. Developers.
Manage your Noctic Account
Don't have a Noctic Account? Create yours now
We sent a six-digit code to your address. Enter it to finish signing in.
No code yet? Check your spam folder. The same email carries a sign-in link that works just as well if you would rather tap it. Wrong address? Contact support.
The code could not be sent, so nothing will arrive. Nobody is signed in and no account was changed. Tell support and we will sort the delivery out.
Five sign-in attempts failed for this account, so we locked it and emailed an unlock link to the registered address. Open that email and follow the link to confirm the account is yours.
The lock lifts on its own in 15:00, or immediately once you use the link.
Continue to
This app is asking to use your Noctic Account.
Connecting as this account. Use Switch if you hold more than one — you will be asked for the password and an emailed code before anything is connected. Access can be revoked at any time from your account.
Sign in to manage your details, your devices and the apps you have connected.
Your account
One account for Shiba, Cadence, Compass and every app you connect with Continue with Noctic.
About you
The details attached to your account. Your name is what apps see when you approve the profile scope; the rest stays with us.
Your date of birth sets age-appropriate features, so it is not editable here. Contact support if it is wrong. Language and text size live in Settings.
Protection
Your email address is your account name. Every sign-in also needs a code we email you, so a password on its own is never enough.
Passwords are checked against known breach corpora in your browser before we accept them — the password itself never leaves this device. More in Security.
Access
Every device signed in to this account, and its recent sign-ins. Sign out any one of them, all the others, or every device including this one, which also revokes the tokens held by the Noctic apps.
Connections
Apps you have approved with Continue with Noctic, what each one was granted, and a button that ends it. Revoking takes effect immediately.
Apps only ever see the scopes you approved. Your date of birth, plan history, moderation records, private notes and assistant conversations are not available through any scope. How the ecosystem works.
Subscription
What this account is on today. Plans are bought inside the product you are using, and cancelling takes effect at the end of the period you have paid for.
Card details are handled by Stripe and never reach our systems. Contact us about invoicing or an education agreement.
Your data
Take a copy whenever you like, or close the account for good. Neither one costs anything and neither needs a conversation with us first.
Deletion removes your profile, posts, notes and generated content across the ecosystem. It cannot be undone and it completes within thirty days. How privacy works.
Apps ask for identity, profile, email or API access — you approve each one.
Remove an app's access at any time from your account settings.
Birthdays, plan history and moderation records are never shared with apps.
Verification earned in one product is recognized across the ecosystem.
Four scopes, no bundles, and nothing granted by implication.
| identity | That you are a real signed-in Noctic user, and a stable identifier for you. Nothing else. |
|---|---|
| profile | Display name, avatar and verification badge. What other users already see. |
| Your email address, so the app can contact you. Requested separately and refusable on its own. | |
| api | Permission to make model requests on your behalf, counted against your plan and shown in your usage. |
Your date of birth, plan history, moderation records, private notes, direct messages and assistant conversations are not available through any scope. There is no partner tier that unlocks them.
A list of every app with access, what it asked for, and when you approved it.
One button ends access at once. There is no grace period and no token that keeps working for an hour.
New passwords are checked against known breach corpora before they are accepted, without the password leaving your browser.
Take a copy of everything, or delete the account and its content across every product, from Settings.
Noctic Developer documentation
Sign-in, keys, Cadence, webhooks and the Program, on one page.
Start
Noctic is one account across Shiba, Cadence, Compass and everything else we make, and building on Noctic means building on that account. There are three ways in.
| Address | What it is for |
|---|---|
developer.noctic.ink | This site: the docs, the platform, keys, tools, examples, Kick Start, the Program, Shouts and events. |
noctic.ink | The Noctic Account itself: sign-in, profile, devices and connected apps. |
shibaai.dev/oauth/authorize | Where your app sends people to sign in and approve it. |
oijfjxqcavxiexnyszbu.supabase.co/functions/v1 | The token and userinfo endpoints. |
api.noctic.ink | Class Sync at /class-sync and the Cadence Teacher API at /teacher. |
Start
From nothing to a signed-in user. You need a Noctic Account — if you are reading this signed in, you have one — and a server that can keep a secret.
state.
?code=shc_…&state=….
Check state is the value you sent before you do anything else.
Try every step against the live endpoints first. The URL builder, token exchange tester and userinfo explorer run in your browser, as you. Put your client ID into Code examples and every sample rewrites itself with it.
Start
Everything on this site happens as your Noctic Account, so every key can be traced to the person who minted it and revoked by them. There is no separate developer login and nothing extra to create.
noctic.ink and developer.noctic.ink are one family of sites and share one session. Sign in on either and the other knows straight away — arrive here from a browser where you are already signed in to Noctic and there is nothing to press. Signing out works the same way: sign out of one and you are signed out of both, on this device.
Not signed in anywhere? Sign in takes you to noctic.ink for your password and the emailed code, and then straight back to the page you were on, signed in.
Chose not to stay signed in? Then the session lasts until you close the browser, on both sites, rather than being kept on the machine.
Everyone who signs in to your app can see it in their Noctic Account with the scopes it holds, and
disconnect it whenever they like. When they do, its tokens stop working immediately, with no grace
period — so treat a sudden 401 as a disconnection and send them back through sign-in rather
than retrying.
Sign in with Noctic
Sign in with Noctic is OAuth 2.0 with the authorisation code grant. Your app never sees a password: people sign in on Noctic, approve the scopes your app asks for, and return to you with a short-lived code that your server trades for tokens.
code and your state.| Endpoint | Address |
|---|---|
| GETAuthorise | https://shibaai.dev/oauth/authorize |
| POSTToken | https://oijfjxqcavxiexnyszbu.supabase.co/functions/v1/oauth-token |
| GETUserinfo | https://oijfjxqcavxiexnyszbu.supabase.co/functions/v1/oauth-userinfo |
A plain link or a redirect. Every parameter goes in the query string.
| Parameter | Required | What it is |
|---|---|---|
client_id | Yes | Your app's client ID. |
redirect_uri | Yes | Where to send the person back. Must exactly match one registered for the app. |
response_type | Yes | Always code. |
scope | No | Space-separated. identity profile email covers most apps. |
state | Recommended | A random value you store and compare on the way back. It is what stops a forged callback. |
code_challenge | Public clients | The PKCE challenge, for apps with no secret. |
code_challenge_method | With a challenge | S256. |
From your server, POST JSON to the token endpoint. The code begins shc_, expires sixty
seconds after it is issued and works once, and redirect_uri has to be byte-for-byte the
one used to get it — it is not where anything is sent this time, it is part of the proof the exchange
belongs to that sign-in.
| Field | What it is |
|---|---|
access_token | A signed JWT. Send it as Authorization: Bearer …. Valid for one hour. |
refresh_token | Gets a new access token without involving the person again. Store it server-side, encrypted, as a credential in its own right. |
expires_in | Seconds until the access token expires. |
scope | What was actually granted, which can be narrower than what you asked for. Read it rather than assuming. |
Access tokens last an hour. Refresh shortly before one expires rather than waiting for a request to fail, and keep the new refresh token that comes back with the new access token.
Single-page and mobile apps ship their code to the people using them, so they cannot hold a client
secret. They send a code_challenge with the authorisation request instead, and prove it
with the matching code_verifier when they exchange the code. The
PKCE generator makes a pair to test with.
One GET with the access token. The response is shaped by what the person approved rather than what you asked for, and a field you were refused is absent rather than empty — check before you read it. Call it once after sign-in and store what you need; it is rate-limited per token.
| Scope | What it adds |
|---|---|
identity | The stable Noctic user ID, sub. Proof of a real account and nothing more. |
profile | Username, display name, picture, plan and verified status — what other people already see. |
email | email and email_verified. Refusable on its own without refusing the rest. |
api | Model requests on the person's behalf, drawn from their plan. No extra profile fields. Granted on request — ask us. |
Date of birth, plan history, moderation records, private notes, direct messages and assistant conversations are not available through any scope, and there is no partner tier that unlocks them.
| You see | What it means |
|---|---|
invalid_grant | The code expired, was already used, or was issued for a different client or redirect URI. Codes are deliberately fragile: start the flow again. |
invalid_client | The client ID and secret do not belong together. Roll the secret on Keys if you have lost it. |
401 from userinfo | The token expired or the person disconnected your app. Refresh once; if that fails too, send them back through sign-in. |
403 from userinfo | The token is fine but lacks the scope. Ask for it in the authorisation URL — a scope cannot be widened afterwards. |
Build
An app is a name, a homepage and one or more redirect URIs, and it holds two credentials.
| Credential | How to treat it |
|---|---|
client_id | Public. It goes in the authorisation URL and names your app on the consent screen. |
client_secret | Private. Shown once, when the app is made or the secret is rolled, and never again. It belongs in an environment variable or a secret manager on your server — not in a repository, a front-end bundle or a screenshot. |
http://localhost while you develop.localhost may use http://. Everything else should be https://.redirect_uri in a request has to match a registered one exactly — scheme, host, port and path.A lost secret cannot be recovered, only replaced. Rolling it on Keys issues a new one, and the old one stops working the moment it does — so have the deploy ready before you roll. Sign out all users on the same page ends every session your app holds, on every device.
Build
Every webhook we send carries its signature in the X-Noctic-Signature header:
sha256= and then the HMAC-SHA256 of the raw request body, keyed with your signing secret,
in lowercase hex. A request whose signature does not match did not come from us — drop it without doing
anything else.
Verify, answer with a 2xx, then do the work. Slow handlers cause retries and retries cause
duplicates, so make the handler idempotent and key it on the event's ID. The
webhook signature tool produces the exact header for a
payload, to test your check against.
Build
Glass is the design language behind everything Noctic makes: system type doing the hierarchy, one blue accent, hairline borders, blurred surfaces over a single background, two corner radii and one motion curve. The design kit packs it as a skill — the rules, every token in light and dark, the components and the way we write — so Claude can build your interface in the Noctic look, or you can read it and build it by hand.
Unzip it where your tools look for skills. After that, ask for the Noctic look — “build the settings page in the Noctic style” — and Claude reads the kit before it writes anything.
| File | What it holds |
|---|---|
SKILL.md | The four layers, the rules we never break, type, colour and a checklist to run before anything ships. |
assets/glass.css | Every token in light and dark, and the components built from them: the glass bar, stages, pill buttons, cards, fields, status pills, code blocks and sheets. Drop it into any site — no build step. |
assets/starter.html | A whole page made from nothing but glass.css, with an appearance switch, to copy from. |
references/components.md | Markup, sizes and states for each component, and the motion table. |
references/voice.md | How we write buttons, headlines, errors and empty states. |
cubic-bezier(.16, 1, .3, 1). With reduced motion it fades instead, and nothing goes missing.The look, not the brand. Use Glass freely in your own product. The Noctic mark, the name and our product names stay ours, so keep them out of your logo, app name and copy — the one place they belong in your app is the button above. The brand guidelines have the detail.
Cadence
A class website, read into a class. Your site sends a manifest of what it publishes — decks, notes, handouts, links — and Cadence fetches each item, pulls the text out of it and files it under the class the key belongs to. Everything a student sees comes from something the teacher posted, and everything Cadence AI says about the subject can be traced back to it.
| Key | Where it lives, and what it can do |
|---|---|
ntk_pub_… | Publishable. It sits in a script tag in plain sight on the class website, so it is locked to the class's own origins and can do one thing: offer material for its class. It cannot read anything back or see a student. |
ntk_sec_… | Secret. Server-side only, for an LMS or CMS plugin. Reads and withdraws material as well as posting it, and is the only key the Teacher API accepts. |
Get both from Class keys. We store a hash of each key, not the key, so a lost one is replaced rather than recovered.
Base URL https://api.noctic.ink/class-sync. Send the key as a bearer token, or in X-Noctic-Key.
| Call | What it does |
|---|---|
POST/verify | Checks a key and returns its class. Changes nothing — call it first, and show the class name so a key pasted into the wrong site is obvious. |
POST/materials | The manifest, up to 500 items. Items already on file are matched on id and updated, so posting the same list on every page load is intended. |
GET/materials | What is held for the class and what happened to each item. Secret key only. |
DELETE/materials?id=… | Withdraws one item from students and from Cadence AI. Secret key only. |
Only id and url are required on an item; title,
kind, topic, checksum and posted_at make it easier
to find and cheaper to sync. A top-level complete: true says the manifest is the whole
class, so anything missing from it is withdrawn — leave it off when you sync one page at a time. The
full Class Sync reference has every field, the file types Cadence
reads, and the drop-in script that does all of this for an ordinary class page.
Cadence
Class Sync handles material. The Teacher API is everything else about a class: its name and term, the sites allowed to speak for it, and the roster — for the schools whose register lives in an SIS or an overnight CSV rather than a web page.
Secret key only, and from a server only. It refuses ntk_pub_ outright and sends no
CORS headers, so a browser will never hand a roster to a script — even if somebody pastes a secret key
into a page.
Base URL https://api.noctic.ink/teacher, the same authentication as Class Sync, and a
budget of 60 calls a minute shared with Class Sync, because it belongs to the key. There is no class ID
to pass: the key is the class.
| Call | What it does |
|---|---|
GET/class | The class, its allowed origins, whether sync is live, and counts of the roster and material. |
PATCH/class | name, subject, school, term, site_origins, live. Fields left out, or sent empty, are left alone — except site_origins: [], which clears them. |
GET/students | The roster. ?include=removed adds people taken off it. |
POST/students | {"handles": ["alice", "@bob"]}, up to 200 at a time. A string is split on commas and whitespace. |
DELETE/students?handle=… | Takes one person off, immediately. Removing somebody already off is not an error. |
Each handle comes back active (they have an account and are on the class), invited (nobody
holds that handle yet — it activates itself when they sign up), already or invalid. A whole
export landing as invited usually means the export has the wrong column in it. The
full Teacher API reference walks through a complete nightly sync.
Reference
Every refusal names itself and, where it can, says what to change. These are the ones worth knowing before you ship.
| Limit | Applies to | What happens |
|---|---|---|
| 60 calls a minute | Each class key, across Class Sync and the Teacher API | 429 rate_limited, with Retry-After in seconds |
| 500 items, 512 KB | One Class Sync manifest | 413 too_many_items; split it |
| 200 handles | One POST /students | 413 too_many_handles; send batches |
| 200 MB | One file read by Class Sync | The item is marked skipped with a reason |
| 60 seconds | An authorisation code | invalid_grant on exchange |
| 1 hour | An access token | 401; refresh it |
| Code | From | Meaning |
|---|---|---|
401 no_key | Teacher API | No bearer token and no X-Noctic-Key. |
401 malformed_key | Teacher API | That is not the shape of a class key. |
401 unknown_key | Both | The key is not active — rolled, revoked or mistyped. Mint a new one under Class keys. |
403 origin_not_allowed | Class Sync | A publishable key used from a site the class does not list. Usually www, staging, or http against a registered https. |
403 read_needs_secret_key | Class Sync | A publishable key tried to read or withdraw. That is the design. |
403 needs_secret_key | Teacher API | You sent the publishable key. |
405 no_browser | Teacher API | A CORS preflight arrived. Call it from a server. |
409 class_paused | Class Sync | The class exists but sync is off. Turn it on under Class keys. |
413 too_many_items | Class Sync | Over 500 items or 512 KB in one manifest. |
413 too_many_handles | Teacher API | Over 200 handles in one call. |
429 rate_limited | Both | Over 60 calls in a minute on one key. Wait for Retry-After. |
Malformed items inside an otherwise good Class Sync manifest are counted in ignored and
rejected rather than failing the call — one bad date should not cost a teacher a term of
material.
Reference
Before you ship, every line of this should be true.
ntk_sec_ key live on a server, in an environment variable or a secret manager.state, and the callback refuses one that does not match.S256, and never a client secret.scope that comes back.401 sends the person back through sign-in instead of retrying in a loop.Found a vulnerability in Noctic itself? Tell us through Security rather than an issue anybody can read.
Reference
Utilities that run in your browser, as you, against the live endpoints. Nothing you type leaves the device except the call you choose to make.
Community
Everything above is free and open to any Noctic Account. The Program is for the things that need a name attached: a verified publisher on the consent screen instead of "an unverified developer", a listing in the Ecosystem, raised limits, pre-release builds, hardware and the labs. Membership is free.
| Membership | For |
|---|---|
| Individual | One person publishing under their own legal name. |
| Organisation | A company publishing under its registered name. Needs an entity number, an email at the organisation's own domain, and someone who can sign for it. |
| Education | A school, college or university. No entity number asked for. |
| Enterprise, in-house | Apps used inside your own organisation and never listed publicly. |
| Status | What it means |
|---|---|
| Draft | Being filled in. Nobody but you can see it. |
| Needs a change | Sent back, by the automatic check or by the team. The note says what to change. |
| Waiting for review | Complete, and with the Developer team. |
| Member | Accepted. The membership is active. |
| Declined | Not accepted this time. The note says why, and Support is the way to ask again. |
Community
Developer Shouts are short posts from the Noctic Developer team — releases, heads-ups about changes, events and anything else worth a developer's attention. They are on developer.noctic.ink/shouts, and the latest three are at the top of the developer home. Pinned shouts stay first while they are still true, and anything that changes how an API behaves is written into these docs as well.
Events — sessions, labs and meetups — are listed on Events when they are scheduled, and you take a seat there with the account you already have. Members of the Program get the labs first.
Community
No. Registering apps, the identity, profile and email scopes,
Class Sync, the Teacher API and the Program are free. Only the api scope draws on a
plan, and it draws on the user's.
Usually because you are not signed in on noctic.ink in this browser either, or you signed out of one of them — which signs you out of both. Press Sign in and you come straight back here. If you are signed in on noctic.ink and still see this, reload the page once and tell us if it persists.
It cannot be recovered, only replaced. Roll it on Keys; the old one stops working as the new one is issued.
Almost always the body: a framework that parsed the JSON has already thrown away the bytes you need. Use its raw-body option, and check for a trailing newline in the secret.
The automatic check answers the moment you submit. A complete application then waits for the Developer team, and the decision appears on your membership page as soon as it is made.
Compose the link your app sends people to.
Not sure what a redirect URI is? Read the plain-English guide in the Field Guide.
Five parameters, and only the first two are compulsory. Everything the builder produces is a plain URL — you can read it, paste it into a browser, and see exactly what your users will see.
| client_id | The public identifier for your app, issued when you register it. Safe to ship in a mobile binary or a front-end bundle; it identifies you but proves nothing on its own. |
|---|---|
| redirect_uri | Where we send people once they have decided. It has to match one of the URIs registered against the app, character for character — including the scheme, any port and any trailing slash. |
| scope |
A space-separated list from identity, profile, email and
api. Ask for the least you need; a short list is approved far more often than a long one.
|
| state | Any random string. We hand it back untouched on the redirect, and comparing it with what you sent is what stops a cross-site request forgery. Optional in the spec, expected in practice. |
| code_challenge | The S256 hash of a secret your app keeps for the length of the flow. Required for anything that cannot hold a client secret — single-page apps, mobile apps, desktop apps. |
Your app opens the URL this page builds. Nothing has been granted yet.
We show who is asking and exactly which scopes. They can approve or refuse each request.
Your redirect URI receives a one-time code and the state you sent, as query parameters.
Your server swaps that code for tokens. The code dies on first use, or after sixty seconds.
The URI in the link is not one of the URIs saved against the app. The comparison is exact, so
http versus https, a stray trailing slash or a missing port will all fail.
Fix it under API keys.
The client ID does not exist, or the app has been deleted. Copy it again from API keys rather than typing it out.
You have asked for a scope the app is not allowed to request. Scopes are set at registration; widen them there first, then rebuild the link.
They refused, or closed the window. That is a normal outcome, not an error — handle it by explaining what your app cannot do without the grant, and offer the link again.
Yes. This page is for checking your parameters while you develop. In production, build the URL in your own code so the state and the code challenge are fresh for every attempt.
A client secret only works if it can stay secret. A single-page app ships its source to the browser, and a mobile app can be unpacked, so neither can hold one. PKCE replaces the secret with a value invented fresh for each sign-in and used exactly once.
A long random string, 43 to 128 characters. Keep it in memory or session storage for the flow.
SHA-256, then base64url with the padding stripped. That result is the challenge.
It rides along on the authorisation URL. The verifier itself never leaves your app.
You send the verifier when exchanging the code. We hash it and compare. No match, no tokens.
An attacker who intercepts the authorisation code still cannot use it, because they never saw the verifier that has to accompany it.
Yes. Reusing a verifier removes the point of it. Generate one when the user starts signing in and throw it away once you hold the tokens.
We only accept S256. The plain method sends the verifier in the clear on the first request, which leaves it in browser history, referrer headers and server logs.
Session storage is the usual answer for a web app, so it dies with the tab. Avoid local storage, and avoid anywhere another origin or another app on the device could read it.
Nine times out of ten the verifier sent at the end does not match the challenge sent at the start — usually because a new one was generated in between, or a page reload cleared it.
The values here come from your browser's own crypto.getRandomValues, so they are
properly random. Use them to test the flow; let your app mint its own in production.
Swap an authorisation code for tokens against the live endpoint.
This calls the live endpoint, so you need a genuine code from a genuine redirect. Codes are single-use and short-lived — if you have already exchanged one, start the flow again to get another.
Begins shc_, arrives as the code query parameter on your redirect URI, and
expires sixty seconds after it is issued.
Byte-for-byte the one used to obtain the code. It is not where anything is sent this time; it is part of what proves the exchange belongs to that authorisation.
For confidential clients only. If your app is a single-page or mobile app, leave it empty and send a PKCE verifier instead.
In production this call belongs on your backend. A secret that reaches the browser is a published secret, whatever the bundler promises.
| access_token | A signed JWT. Send it as Authorization: Bearer …. Valid for one hour. |
|---|---|
| refresh_token | Exchanges for a new access token without involving the user again. Store it server-side, encrypted, and treat it as a credential in its own right. |
| expires_in | Seconds until the access token dies. Refresh before that, not after a request has already failed. |
| scope | What was actually granted, which may be narrower than what you asked for. Read it, do not assume it. |
The code has expired, has already been used, or was issued for a different client or redirect URI. Codes are deliberately fragile. Run the flow again.
The client ID and secret do not match a registered app. Roll the secret from API keys if you have lost it.
Both stop working immediately. There is no grace period. Treat a sudden 401 as a revocation and send the user back through authorisation rather than retrying.
This page splits the token on its dots and base64-decodes the middle part. That is all a decode is — nothing here checks the signature, and nothing here leaves your browser. Anybody can read a JWT; only your server, holding the right key, can tell whether to believe it.
The signature against our published keys, then exp, then iss, then
aud against your own client ID. In that order, and reject on the first failure.
The alg field is supplied by whoever made the token. Pin the algorithm you expect in
your verification code rather than reading it back out of the token.
A JWT is signed, not encrypted. Every claim inside is readable by anyone holding the token, which includes the browser it passed through.
Expiry is compared against your server's clock. A drifting clock produces tokens that look expired on arrival, or ones that outlive their welcome.
| sub | The stable Noctic user ID. This is the value to store against your own records. |
|---|---|
| iss | Who issued the token. Always a Noctic issuer for tokens from our endpoints. |
| aud | Who it is for. Should be your client ID; if it is not, the token is not yours to accept. |
| exp | Expiry as a Unix timestamp. One hour after issue for an access token. |
| iat | When it was issued. Useful for spotting a clock-skew problem between machines. |
| scope | What the user actually granted. Enforce this on every request, not just at sign-in. |
Present only when the email scope was granted and approved. |
A user ID is stable for the life of the account. An email address is not — people change them. Key your
database on sub.
Call the profile endpoint with a token and read the response.
The response is shaped by what the user approved, not by what you asked for. A field you were refused is absent rather than empty, so check for its presence before you read it.
| identity | sub only — proof of a real signed-in account and a stable identifier for it. |
|---|---|
| profile | name, picture and verified. What other users already see. |
email and email_verified. Requested separately, and refusable on its own
without refusing the rest.
|
|
| api | No extra profile fields. It grants model requests against the user's plan, nothing more. |
Date of birth, plan history, moderation records, private notes, direct messages and assistant conversations are not available through any scope, and there is no partner tier that unlocks them.
No. Call it once after sign-in, store what you need, and refresh it occasionally — daily is plenty. The endpoint is rate-limited per token, and a chatty integration will hit that limit.
It has expired or been revoked. Refresh it once; if the refresh also fails, the user has withdrawn access and needs to authorise again.
The token is fine but lacks the scope. Ask for it in the authorisation URL — you cannot widen a scope after the fact.
Either the profile scope was refused, or the account has no display name set. Fall back
to something neutral rather than showing an empty space.
Cache it, but re-fetch periodically. Avatar URLs change when someone updates their picture, and the old URL stops resolving.
Every webhook we send carries an HMAC-SHA256 signature over the raw request body, computed with your signing secret. Recompute it on your side and compare. If the two differ, the request did not come from us and should be dropped without further processing.
The exact bytes received, before any JSON parsing. Re-serialising changes them and breaks the hash.
SHA-256, keyed with your signing secret, rendered as lowercase hex.
Use your language's timing-safe comparison. A plain equality check leaks the answer a byte at a time.
Reject anything older than five minutes, so a captured delivery cannot be replayed at you later.
Almost always the body. A framework that parses JSON and hands you an object has already thrown away the bytes you need — reach for the raw-body option your framework provides.
Check for a proxy that rewrites the body, and check for a trailing newline added by a shell when you copied the secret into an environment variable.
Verify, acknowledge with a 2xx, then process. Slow handlers cause retries, and retries cause duplicates. Make your handler idempotent and key it on the event ID.
Roll it from API keys. Deliveries signed with the old secret stop verifying at once, so deploy the new value before you roll.
It is signed, not encrypted — the transport is HTTPS. The signature proves who sent it and that nothing was changed on the way; it does not hide the contents from anything terminating your TLS.
One form. Credentials in seconds.
Your client secret is shown once, immediately after the app is created. Store it somewhere safe — it is never displayed again.
Registration takes about a minute, and nothing here is permanent — every field can be changed afterwards from API keys.
It appears on the consent screen, above the list of scopes. Use the name your users know the product by, not an internal codename.
Somewhere a curious user can go to work out who you are. Optional, but apps without one are approved
less often when they ask for more than identity.
Where we send people after they decide. Add every environment you will actually use — production,
staging and http://localhost for development.
An environment variable or a secret manager. Not a repository, not a front-end bundle, and not a screenshot in a chat thread.
A client ID you can publish, and a client secret shown exactly once on this page.
Where you can edit URIs, roll the secret, grab the button markup or delete it entirely.
Authorisation URL, then code exchange. Our tools will check each step against the live endpoints.
New apps start with identity, profile and email. Ask us if you need api.
No. Registering an app and using identity, profile and email
is free and always will be. Only the api scope draws on a plan, and it draws on the
user's, not yours.
Yes, and you should — separate credentials for production and development mean a leaked development secret cannot touch real users.
It cannot be recovered, only replaced. Roll it from API keys; the old one stops working the moment the new one is issued, so deploy carefully.
Not for the three default scopes. Apps requesting api are looked at by a person first —
write to support with what you are building and roughly what volume you expect.
Profile data obtained through sign-in may not be sold, brokered or merged into a third-party graph. The full terms are in the legal centre.
Everything you hold, in one place.
Two kinds live here. App keys are for signing people in with Noctic. Class keys are for a teacher pushing their own material into Cadence. They have nothing to do with each other except that they are both yours, and both were easier to find in one place than in two.
A key you paste into the class website you already keep. Every deck, set of notes and handout that appears there arrives in Cadence under that class, and Cadence AI answers your students out of the slide you actually taught from. You say who those students are, and only they can read it.
Pick an app above, then copy the markup. It renders the official Continue with Noctic™ element and sends people through the authorisation flow.
Preview
Markup
Choose an app above to generate your snippet.
A client ID is public by design. A client secret is a password for your app, and everything that applies to a password applies to it.
If a secret is in a browser bundle or a mobile binary, it is published. Public clients use PKCE instead, which is designed for exactly that situation.
Environment variables or a secret manager. A secret committed once lives in the history for good, even after the file is deleted.
Twice a year is a reasonable habit, and immediately whenever somebody who had access leaves. Rolling is instant and takes no downtime if you deploy the new value first.
Separate registrations for production, staging and local work. It keeps redirect URIs honest and limits the blast radius of a mistake.
| Roll the secret | Issues a new secret and invalidates the old one at once. Existing access tokens keep working until they expire; new exchanges need the new secret. Deploy the new value before you roll. |
|---|---|
| Edit redirect URIs | Takes effect immediately. Removing a URI breaks any flow already in progress against it, so change them at a quiet moment. |
| Delete the app | Permanent. Every token and every grant is revoked on the spot, and the client ID is not reissued. Users see the app disappear from their connections list. |
If you believe a secret has leaked, roll it first and investigate afterwards. Then tell us at support so we can look for unusual use of the old one.
The name is what your students will see above the material in Cadence, so use the one they call it. The site is the address your class pages actually live at — the publishable key only works from there.
Publishable key — this one goes in your class website.
Secret key — server-side only, and shown once. Skip it unless you are wiring up an LMS.
Sync starts paused. Paste the snippet below, check it says the right class, then turn the class on.
Pick a class above, then drop this into the template your class pages share — the footer is usually right. It reads the page you already publish and sends a list of what is on it. Nothing about a student is read, and nothing is uploaded but the addresses of your own files.
A key decides what reaches Cadence. The roster decides who reads it. They are separate on purpose: your class website is public, and the material Cadence holds for your class is not.
Add people by the username you already know them by — @alice — from the
Students button on the class above. Paste a whole register at once if you have one;
commas, spaces and new lines all work, and the @ is optional.
If it belongs to a Noctic Account, that student can study the class from the next time they open Cadence. Nothing to accept, no invitation email.
Writing next term's roster before the students have accounts is the ordinary case. The handle is held, shown as unfinished, and grants nothing at all until somebody claims it.
A student on the roster sees the class name and the material that is still published. They cannot see your keys, your other classes, or who else is on the roster.
Take a handle off and access goes at once. The name stays visible to you as removed, so a student who left mid-term does not quietly vanish from your own record of the class.
Take a deck down from your class site and it stops being readable for everybody on the roster at the same moment — the roster grants access to what you currently publish, not to an archive of it.
A key pasted into a web page is published, whatever anybody intended. So the key meant for that job is built to survive being read by a stranger, and the key that is not is never asked to go there.
ntk_pub_…Publishable |
Lives in the page in plain sight. It can offer material for its own class and do nothing else — it cannot read the class back, cannot see a student, cannot reach another class, and is refused outright from any site but the ones you named. Somebody who copies it out of your source can, at worst, offer your class a link you will see in the list below and remove. |
|---|---|
ntk_sec_…Secret |
For a server: an LMS plugin, a static-site build step, a nightly job. It also lists and withdraws material, and it is not origin-locked, which is exactly why it must never appear in a page. Treat it as a password. |
Both are scoped to one class. A key cannot be talked into touching a class it was not minted for, so the worst case for a leaked key stays inside the room it came from.
The deck goes on the class page the way it always has. There is no second place to upload it to.
Slides, speaker notes, headings and handouts are pulled apart into text, kept against the class, and dated to when you published them.
Students in that class see the material where they already look, next to the lesson it belongs to in the calendar.
Cadence AI answers from your slide 14 and quotes it, instead of answering from the internet's idea of the topic. When it has nothing from you, it says so rather than inventing it.
No, and the point of this is that you do not. Class Sync reads the site you already keep, wherever it is hosted — a school CMS, Google Sites, WordPress, a folder of static pages. If you can paste a script tag into the template, it works.
Add them anyway. The handle is held against the class and shown as unfinished, granting nothing until somebody actually holds it — at which point they get access without you doing anything else. This is why you can write September's roster in August.
A handle is unique to one Noctic Account, so a correctly typed one reaches exactly that person and a mistyped one reaches nobody — it simply waits, unclaimed. The chips on the class show you which is which before anything has been read.
No. A student can see that they are on a roster and can read the class material; the register is yours. Knowing you are in a class is not the same as being handed the list.
Only what your class site publishes is ever sent, so a draft that is not on the site does not exist as far as we are concerned. Take a deck down and it is withdrawn from Cadence on the next sync.
They are skipped, and the list below says so. Cadence fetches your material as an anonymous visitor; anything it cannot open, it will not guess at. Use a secret key from your server if you need to push material we cannot reach ourselves.
No. Class material is read to answer questions for the students in that class and for nothing else. It is not training data, it is not pooled across schools, and deleting the class deletes it. The legal centre has the wording that binds us to that.
Check the class is turned on — sync starts paused deliberately — and that the address in your
browser's bar matches the site you registered, www included. The list above shows the
last time each key was used, which is usually enough to tell "not reaching us" from "reaching us and
refused".
It would only ever add to your class, and you would see it in the material list. If you share a class site between several teachers, register the class once and mint a key each, so a key can be rolled without disturbing anybody else.
A class website, read into a class.
One endpoint. You send a manifest of what your class site publishes; we fetch each item, pull the text out of it, and file it under the class the key belongs to. Everything a student sees comes from something you posted, and everything Cadence AI says about your subject can be traced back to it.
Base URL https://api.noctic.ink/class-sync. Authenticate with the key as a bearer token, or
in X-Noctic-Key if a bearer header is awkward where you are.
| POST /verify | Checks a key and returns the class it belongs to. Costs nothing and changes nothing — call it first, and show a teacher the class name so a key in the wrong template is obvious immediately. |
|---|---|
| POST /materials |
The manifest. Up to 500 items in one call. Items already on file are matched on id and
updated, so posting the same list on every page load is the intended way to use this, not a mistake.
|
| GET /materials | What we hold for the class and what happened to each item. Secret key only — a publishable key cannot read anything back. |
| DELETE /materials?id=… | Withdraws one item. It stops being visible to students and stops being quoted. Secret key only. |
Only id and url are required, and id falls back to the URL when
you leave it out. Everything else makes the material easier for a student to find and for Cadence to
place in the term.
| id | Your own identifier for the item — a slug, a CMS post id, a file path. It is what makes the second sync an update rather than a duplicate. Keep it stable across renames; the title can change freely. |
|---|---|
| url |
Where the file actually is. It must be reachable without signing in, or the item is marked
skipped and no student sees a broken link.
|
| kind |
slides, notes, handout, reading,
syllabus, assignment, link or document. Leave it
out and we take it from the file extension, which is right nearly always.
|
| checksum | Anything that changes when the file does — an ETag, a hash, a last-modified stamp. When it has not moved we skip the fetch entirely, which is most of the cost of a sync and all of the load on your server. |
| topic | The unit or chapter, in your words: "Unit 3 — Reconstruction". It is what lets a student ask about a unit rather than a filename, and what Cadence cites back to them. |
| posted_at | When you published it. Cadence lines material up against the calendar with this, so a student revising last Tuesday's lesson gets last Tuesday's deck. |
| complete |
Top-level, not per item. true says the manifest is the entire class, so anything missing
from it is withdrawn. Leave it off when you sync one page at a time, or a single page will retire the
rest of the term.
|
The drop-in script covers the ordinary case: a class page with links on it, and Class keys writes it for you with your own key in it. The rest is for when you have a real CMS and would rather push than be scraped.
Put your publishable key in and the browser examples rewrite themselves with it. The server-side ones read a secret key out of the environment instead, and always will — a secret key that has been through a web page is not a secret any more.
Nothing you type here is sent anywhere. Get a key from Class keys.
A slide deck is not a wall of text and we do not treat it as one. Cadence keeps the structure, because a student asking "what was on the slide about the New Deal" is asking about a slide.
.pptx, .ppt, .key and .odp. Titles, body text,
tables and — the part that usually matters most — the speaker notes, kept per slide and numbered, so
an answer can point at slide 14 and mean it.
Text and headings by page. A scanned worksheet is read with OCR; if the scan is too poor to trust,
the item is marked failed rather than indexed as nonsense.
.docx, .odt, .rtf, .md, .txt and
Pages. Headings become structure, so a document's own sections survive into what a student can ask
about.
A link item is read as an article: the content of the page, without the navigation and
the cookie banner. Useful for a syllabus that lives as a web page rather than a file.
.xlsx and .csv, read as tables with their headers. Mark schemes and data
sets stay legible instead of collapsing into a run of numbers.
Video and audio, anything behind a login, anything over 200 MB, and anything that is not one of the above. Skipped items are listed under the class with the reason, never silently dropped.
| 500 items per call | Per manifest, not per class. Send a term at a time if you have more. |
|---|---|
| 512 KB per manifest | This is a list of addresses, not the material. If you are anywhere near it, you are probably sending file contents by mistake. |
| 60 calls a minute per key | Plenty for a class site, and low enough that a key found in somebody's page source is not worth much. The drop-in script syncs once a page load and no more. |
| 200 MB per file | Above that the item is skipped with a reason. Split a term-long deck; students prefer it too. |
| Unchanged items are free | Same checksum, no fetch. A site that posts its whole manifest on every page load costs one database statement, which is why we would rather you did that than tried to be clever about it. |
401 unknown_key |
The key is not active — rolled, revoked, or mistyped. Mint a new one under Keys. |
|---|---|
403 origin_not_allowed |
A publishable key used from a site the class does not list. Almost always www, a
staging domain, or http against a registered https. Add the exact origin.
|
403 read_needs_secret_key |
A publishable key tried to read or withdraw. That is the design, not a fault. |
409 class_paused |
The class exists but sync is off. Turn it on under Keys once the snippet reports the right class. |
429 rate_limited |
Over sixty calls on one key in a minute. Retry-After says how many seconds are left in
the window. The drop-in script syncs once a page load, so if you are seeing this from a class site,
something is calling in a loop.
|
413 too_many_items |
Over 500 in one manifest, or over 512 KB. Split it. |
Every refusal names itself and, where we can, says what to change. Malformed items inside an otherwise
good manifest are counted in ignored and rejected rather than failing the
call — one bad date should not cost a teacher a term of material.
The class, and who is on it.
Class Sync handles material: your site says what it publishes and Cadence reads it. This is everything else about a class — what it is called, which sites may speak for it, and the register. It takes the same key, so if your class site is already syncing you have one already.
It exists for the schools whose register is not a web page. If your students arrive from an SIS, a CSV overnight or a script somebody wrote in 2019, this is how the roster stays right without a teacher retyping it into Class keys every September.
Before anything else
A publishable key lives in a <script> tag on a page anybody can read. A register is a
list of children’s handles. Those two facts are not allowed to meet, so this endpoint refuses
ntk_pub_ outright — not a reduced view of the roster, no view of it.
It also sends no CORS headers at all. That is deliberate and it is the same decision said a second way: a browser will not hand the response to script even if somebody does paste a secret key into a page. The request may leave; nothing comes back. Call this from a server.
https://api.noctic.ink/teacherX-Noctic-Key. Same as Class Sync.GET /class |
The class, its allowed origins, whether sync is live, and counts of the roster and the material we hold. Call it first: a wrong key pointed at a real class is obvious here and expensive later. |
|---|---|
PATCH /class |
name, subject, school, term,
site_origins, live. A field you leave out is left alone, and so is one you
send empty — the same rule the developer page follows. The exception is
site_origins: [], which clears them, because withdrawing a site’s permission has
to be sayable.
|
GET /students |
The roster. ?include=removed adds people taken off it. Each entry carries a status and
whether that handle has a Noctic account yet.
|
POST /students |
{"handles": ["alice", "@bob"]}, up to 200 at a time. A string works too and is split on
commas and whitespace, because that is what comes out of a spreadsheet cell. You get a result per
handle and a tally.
|
DELETE /students?handle=… |
Takes one person off. Access goes immediately. Removing somebody who is already off is not an error — a nightly sync should not have to remember what last night did. |
invited usually means the export has the wrong column in it.The shape almost everybody wants: read what we hold, compare it with the register you already have, and send only the difference. Adding somebody twice is harmless, so the safe version of this is the one that does not try to be clever.
const KEY = process.env.NOCTIC_TEACHER_KEY; // ntk_sec_…
const BASE = 'https://api.noctic.ink/teacher';
const head = { Authorization: `Bearer ${KEY}`, 'Content-Type': 'application/json' };
// 1 · Check the key points where you think it does.
const { class: cls } = await fetch(`${BASE}/class`, { headers: head }).then(r => r.json());
console.log(`${cls.name} — ${cls.students.active} active, ${cls.students.invited} invited`);
// 2 · What we hold, and what your register says.
const { students } = await fetch(`${BASE}/students`, { headers: head }).then(r => r.json());
const held = new Set(students.map(s => s.handle));
const should = new Set(await registerFromYourSIS()); // your side
// 3 · Send only the difference.
const adding = [...should].filter(h => !held.has(h));
if (adding.length) {
const out = await fetch(`${BASE}/students`, {
method: 'POST', headers: head, body: JSON.stringify({ handles: adding }),
}).then(r => r.json());
console.log(out.tally); // { active: 24, invited: 2 }
}
for (const h of [...held].filter(h => !should.has(h))) {
await fetch(`${BASE}/students?handle=${encodeURIComponent(h)}`,
{ method: 'DELETE', headers: head });
}
Watch the invited count on the way out. It is the number of names that matched nobody, and
on a first run against a real school it is the only line that tells you the handles in your export are
actually Noctic handles.
401 no_key | No bearer token and no X-Noctic-Key. |
|---|---|
401 malformed_key | That is not the shape of a teacher key. |
401 unknown_key | Not active. Roll it from Class keys. |
403 needs_secret_key |
You sent the publishable key. This endpoint takes ntk_sec_ and nothing else. |
405 no_browser | A preflight arrived. There is no browser case here. |
429 rate_limited |
Over 60 calls in a minute on this key. Retry-After says how long. |
413 too_many_handles | Over 200 in one call. Send them in batches. |
Working examples for every part of the flow.
Put your client ID and redirect URL in the two boxes and every example below rewrites itself with your own values. Nothing you type here is sent anywhere — it stays in this browser.
Your client secret never goes in front-end code. Keep it on your server, in an environment variable.
A plain link is enough. This is the official button, styled for light and dark.
Noctic sends the person back to your redirect URL with ?code=…&state=…. Your server
trades that code for an access token. This must happen server-side.
One GET with the access token returns the person's Noctic identity: id, username, name, picture, and email when the email scope was approved.
Access tokens are short-lived. Use the refresh token to get a new pair, and revoke when someone signs out.
Make it yours.
Everything here applies to your Noctic Account, so a change made once follows you into Shiba, Cadence, Compass and anything else you sign in to. Preferences save the moment you set them.
Thank you — following the emailed link confirmed the account is yours, and the lock has been removed. If those failed attempts were not you, set a new password below before you carry on.
Sign in to sync these preferences across your devices.
Signed out, your choices are remembered on this device only.
How Noctic looks on this device. Text size and accent colour are stored locally, so a shared computer never carries your choices to somebody else's session.
Used for links, highlights and focus rings across every page.
Scales body copy without changing the layout.
Page transitions, reveals, and the scenes on the Aeon™ pages. Matching your device follows its own setting — Reduce motion on a Mac or iPhone, Animation effects on Windows, which battery saver also turns off. Matched, scenes still play without anything sliding or zooming.
Marks links by shape as well as colour, which helps if colour is hard to distinguish.
Noctic follows your device language by default. Choosing one here overrides it.
Left to match your device, Noctic follows your operating system's own reduce-motion setting: nothing slides, zooms or drifts, and the scenes on the product pages still play without moving. The other two choices override it here, on this device. See Accessibility for the rest of what we support.
Choose what reaches you and when. Security messages are the one thing we always send — a sign-in code or an unlock link has to arrive even if everything else is off.
Confirmation codes, unlock links, new-device alerts and password changes.
Occasional notes when something you use gains a feature worth knowing about.
New work from the research team, including model cards and evaluations.
Someone replies to you, mentions you in a channel, or sends a direct message.
The nudge before a planned session, and the nightly check-in.
Company announcements. Roughly one email a month, never more.
In-app notifications appear the next time you open the product.
Nothing but security messages between these times, in your local timezone.
Collects everything non-urgent into a single message each Monday.
We do not sell your address, and marketing mail is off unless you switch it on. Every email we send carries a one-click unsubscribe.
What other people can see, and what we are allowed to learn from your use. The defaults are the private ones — nothing here has to be switched off to protect you.
Your display name, avatar and verification badge.
Lets someone who already knows your address find your profile. Off hides you from search.
Displays a quiet presence dot in Cadence channels and direct messages.
Aggregate counts of which features are opened. No message content, ever.
Lets Shiba and Compass use your recent activity to order what they show you first.
Off by default. Your conversations are never used for training unless you turn this on, and turning it off again stops future use immediately.
How your account is protected, and how to end access you no longer want.
Required. Every registration and every sign-in finishes with a six-digit code sent to your address, so a password on its own is never enough.
Five wrong passwords lock the account for fifteen minutes and send an unlock link to your registered address. Following that link lifts the lock at once.
An email whenever your account is used on a device we have not seen before.
Choose something long. New passwords are checked against known breach corpora before we accept them, and the check happens in your browser — the password itself never leaves this device.
We will email a six-digit code to confirm the change before it takes effect.
Enter the six-digit code we sent to your address. Your password is not changed until the code checks out.
Signing out everywhere revokes every token on every device, including the Noctic apps. You will need your password and a fresh code to get back in.
Not signed in
When this account was signed in to, how, and from which network address.
Apps you have approved with Continue with Noctic hold their own tokens. Review and revoke those from your Noctic Account, or read how the grants work in Security.
Take a copy whenever you like, or close the account for good. Neither one costs anything and neither needs a conversation with us first.
Downloads your profile and every preference on this page as a JSON file you can read or keep.
Puts appearance, notifications and privacy back to their defaults on this device.
Removes your account and its content across every Noctic product. This cannot be undone. Type DELETE to confirm, and we will action the request and email you when it is finished.
What we keep, and for how long, is set out in the Privacy Policy. Backups roll off within thirty days of a deletion.
Billing, plans, treats and model behaviour. Search the Field Guide.
School registration, verification and calendar imports. Common answers.
Sign-in issues, connected apps and privacy requests. Manage your account.
Privacy Policy and Terms of Service, in the legal centre.
One form, one inbox, a real person. We usually answer within a day.
We will send a copy to your email so you have a record of it.
These are the times we hold ourselves to, not the times we hope for.
| General questions | One working day. Usually the same day. |
|---|---|
| Billing and plans | One working day. Refund decisions are made in the first reply, not after a review cycle. |
| School and district | One working day, from the person who knows your campus. |
| Privacy requests | Acknowledged in seven days, completed within thirty. |
| Accessibility reports | Acknowledged in two working days, assessed within ten. |
| Security reports | Same day, including weekends. |
| Anything involving a student's safety | Immediately, ahead of everything else in the queue. |
If something stopped working for everyone at once, it is probably us and probably already posted. Service status.
Verification, calendar imports, plan changes and sign-in problems are answered there in more detail than an email will give you. Field Guide.
A signed-out reload in a private window rules out half of all sign-in reports in about thirty seconds.
Connected apps, appearance, plan and deletion are all in Settings and take effect immediately.
The difference between one reply and four is usually three lines of detail.
The steps you took, in order, ending with the thing that failed.
Sometimes the product is working as designed and the design is the problem. We want to know that.
The exact wording of any error message, or a screenshot with other people's names removed.
Browser or app, device, and roughly when. Never send us a password or a full API key.
| Security | Report a vulnerability through Contact marked security. We reply the same day, we will not threaten you for reporting in good faith, and we credit researchers who want it. Please do not test against real student accounts. |
|---|---|
| A student at risk | Contact your school's moderators first, because they can act immediately. Tell us as well and we will prioritise it above everything else in the queue. |
| Privacy and data requests | Access, correction, export and deletion. Parents and guardians should read Children and Students first, since we verify the relationship before acting. |
| Legal and copyright | Notices and counter-notices go through the legal centre. |
| Press | Announcements are in the Newsroom; asset requests go through Brand. |
| Developers | API keys, OAuth and webhooks are documented under Developers. |
We answer in English and French. There is no phone queue and no chatbot in front of the inbox: every reply is written by someone who can actually change the thing you are writing about.
In development · Preview 2026
An AI that knows your school year — and works ahead of it.
Compass reads the timetable, assignments and notes already living in Cadence, then plans the term with you: what to study tonight, what's about to collide, what your grades need, and where it all leads after graduation.
Compass only proposes work that the timetable, deadlines and grade trend in Cadence actually justify.
Turns deadlines, tests and shifts into a realistic study schedule that rebuilds itself when something moves.
Finds the specific concept you're losing marks on and tutors that — not the whole chapter.
Flags the week three tests land together, early enough to actually do something about it.
Maps course choices, grades and interests to programs, scholarships and apprenticeships worth applying to.
| The data | Cadence already holds the timetable, notes, PED days and assessments. Compass doesn't ask students to enter anything twice. |
|---|---|
| The intelligence | Shiba supplies reasoning, vision for scanned handouts, and voice for hands-free review. |
| The identity | The Noctic Account carries verification, so a school can trust who is on the other side. |
| The distribution | Every Cadence student is one toggle away from Compass. No new app to install. |
Compass explains, quizzes and drafts outlines. It refuses to hand in work for you.
Schools see participation, never private notes or messages.
Every school-facing report is generated from data the student can see first.
Compass reads nothing until the student turns it on, scope by scope.
Cadence and Compass, licensed for your whole school.
Announcements that actually get read, a calendar that matches the real timetable, verified student identity, and an AI study coach — under one district agreement.
| Verified rosters | Student ID scanning ties accounts to real students, so channels stay closed to outsiders. |
|---|---|
| Official channels | Grade, homeroom and campus-wide channels with broadcast rights for staff. |
| Shared calendar | Holidays, PED days and conditional PED days pushed once, visible everywhere. |
| Timetable import | Students photograph a printed schedule; AI turns it into a live calendar. |
| Moderation | Reporting, review queues and staff moderators with full action history. |
| Bulletin board | Clubs, tryouts and lost-and-found on a board students actually check. |
Claim your campus in Cadence and verify with a staff ID.
Grades and homerooms generate automatically; staff get broadcast rights.
Import the calendar once — holidays and PED days included.
Opt in per grade, with student consent for every data scope.
Most schools are through all four steps inside a week. Nothing here needs a server, a plugin or an IT project.
Who it's for
One place to reach the whole campus, and a record of who announced what. Verified rosters mean the audience is exactly the school, and moderation history is exportable when you need it.
Post once to a homeroom instead of chasing a group chat you don't control. Broadcast rights are granted per channel, so a message from staff reads as a message from staff.
The timetable, the holidays, the club sign-ups and the actual announcements in one feed, on the device they already carry. No public follower count to perform for.
A clear answer about what the school can see and what it cannot, and a route to request or delete a student's data that goes to a person rather than a form.
Everything below is included. There are no per-feature add-ons.
Every enrolled student and every member of staff, on any number of devices. Licensing is by school rather than by seat, so a class that grows in October does not become a procurement conversation.
Campus-wide, grade and homeroom channels generated from the roster, plus channels staff create by hand for teams, trips and clubs. Broadcast rights are set per channel.
Term dates, holidays, PED days and conditional PED days entered by one owner and visible to everyone the moment they save. Students layer their own timetable on top.
A student photographs the printed schedule they were handed in September and gets a live calendar from it. No template, no data entry, no asking the office to re-export anything.
Tryouts, auditions, club sign-ups, lost and found. The paper board that nobody reads, in the place students already look.
Reporting, a review queue, named staff moderators and a full action history with reasons recorded. Every decision is attributable to a person.
The study copilot can be enabled per grade rather than all at once, and each student approves the data it may read before it reads anything.
Being clear about this up front saves everyone a procurement cycle.
| Not the official record | Cadence does not hold grades, transcripts or attendance. Your student information system remains the system of record and we do not try to replace it. |
|---|---|
| Not a surveillance tool | There is no administrator view of private notes, direct messages or assistant conversations, and there is no way to buy one. See Children and Students. |
| Not a marking platform | Assignments can be announced and dated. Submission, marking and feedback stay wherever your school already does them. |
| Not a device manager | We do not install profiles, restrict devices or report on what a student does outside our app. |
One member of staff with a school ID to claim the campus and approve the first moderators.
A list of grades or homerooms. A spreadsheet is enough; there is no integration to build.
One person responsible for term dates, so the year is entered once and stays correct.
Your existing conduct policy, applied to a channel. We supply the tooling, not the rules.
The long version is in the Privacy Policy and on the Children and Students page. This is what a district usually asks first.
| Who owns school content | The school. Announcements, channels and the calendar stay with the campus. |
|---|---|
| Who owns private content | The student. Notes, direct messages and assistant history are not visible to staff. |
| Advertising | None, anywhere, on any plan. We do not build advertising profiles of students. |
| Model training | Private student content is not used to train models. |
| Leaving | A school can export its channel and moderation history and close its campus. Student accounts survive the school leaving, because they were never the school's to delete. |
| Requests | Parents and guardians can ask for access, correction or deletion. We verify the relationship, reply within seven days and finish most requests inside thirty. |
A live walkthrough with whoever is claiming the campus, covering channels, rights and the calendar.
A short session for teachers on broadcasting, moderation and what students can and cannot see.
We look at the calendar and rosters with you before the year opens, when mistakes are cheap to fix.
School email goes to a person who knows your campus, not to a general queue.
No. Verification ties an account to a real student through the school's own roster and ID check, so it works for campuses that do not issue student email at all.
No, and there is no setting that turns this on. A moderator sees a specific message only when it is reported, and only in the context of that report.
Their access to the old campus ends when the school removes them from the roster. The account, its notes and its calendar move with the student and can be attached to the new school.
Yes. It is off until a school enables it, it can be enabled for some grades and not others, and each student still approves what it may read.
It runs in a browser and as an app. There is nothing to install centrally and no management profile to deploy.
Reports reach your moderators, not ours. Your staff act under your conduct policy, with a logged history of what was decided and by whom.
Parent accounts are not part of the current licence. Parents can make data requests about their own child at any time through Contact.
By campus under a single agreement rather than per seat. Figures for your school size are on the Pricing page or from us directly.
Plans
Noctic Plus and Noctic Pro carry Shiba, Cadence, Momentum and Compass on one yearly bill. Switch off an app you will not use and the price comes down with it.
Included apps — switch off anything you will not use
Billed yearly. Cancel any time.
A daily allowance across chat, images and code, Cadence in full, and a Noctic Account that works everywhere. No card, no time limit.
Plans renew yearly and cancel instantly if a payment fails — access is revoked the moment billing lapses, never silently continued. Card details are handled by Stripe and never reach our systems.
Every product is included on every plan. What moves is how much and how hard.
| Daily treats | Free gets a daily allowance across chat, images and code. Noctic Plus raises it substantially and Noctic Pro raises it again. Treats reset on a rolling daily window rather than at midnight in one time zone. |
|---|---|
| Effort tiers | Free reaches Medium. Noctic Plus opens High and Plus effort. Noctic Pro unlocks Ultra. A harder tier thinks for longer and costs more treats per request. |
| Cadence | Free everywhere a school has licensed the campus. Cadence Air on Plus and Cadence Pro on Pro add group spaces, analytics and the staff tools on top. |
| Momentum | Momentum Plus syncs streaks and the evening check-in across devices. Momentum Pro adds long-range trends, exports and shared habits. |
| Compass | Compass Light plans one term at a time. Compass Plus plans the whole degree, with transcripts and advisor sharing. |
| Voice, research and market data | Plus and above. |
| Peak-hour priority | Plus and Pro are served ahead of Free when demand is high. |
| Dropping an app | An app you switch off is simply not part of the plan: it falls back to its Free tier and the yearly price drops by that app's share. Add it back whenever you like and the change is prorated. |
A treat is one unit of work. A short answer costs one; a long piece of reasoning, an image or a multi-step agent run costs more, because it genuinely uses more.
The effort tier is a control you set, and the cost of a request is shown before you send it.
Treats reset daily. We do not sell packs that quietly lapse at the end of a month.
Lower effort tiers keep working when the higher ones are spent, so you are never fully locked out.
Consumer plans cannot bill you more than the plan price. There is no metered spillover to discover later.
| Renewal | Yearly, on the day you subscribed. The date and amount are shown in your Noctic Account before it happens. |
|---|---|
| Cancelling | One button in Settings, effective immediately, with no retention offer and no cancellation survey. You keep the plan until the period you paid for ends. |
| Failed payments | Access ends at once rather than continuing on credit. Nothing is charged again without your action. |
| Refunds | If something we shipped stopped the plan being usable, write to us and we will refund it. The decision is made in the first reply, not after a review cycle. |
| Changing plans | Upgrades and added apps apply immediately and are prorated. Removing an app or moving from Pro to Plus takes effect at the end of the year you have paid for. |
| Card details | Handled entirely by the payment processor. Card numbers never reach our systems. |
| Price changes | Announced at least thirty days ahead. An existing plan keeps its price until the notice period ends. |
A campus licence covers every enrolled student and every member of staff under one agreement, rather than charging per seat. A class that grows in October should not become a purchase order.
The Free plan is the trial. It is not time-limited, it includes Cadence in full, and it does not ask for a card.
It drops to its Free tier rather than disappearing. Your data stays exactly where it is, and adding the app back later picks up where you left off.
Not for Cadence. Where a school licenses the campus, the school pays and students use it at no cost. A student can still buy a personal plan for Shiba if they want the higher tiers.
Nothing is deleted. Conversations, notes and posts stay where they are; only the limits change.
Noctic Plus and Noctic Pro are yearly, which is how they cost what they cost. Campus agreements are annual too, invoiced rather than charged to a card.
Campus licensing is already priced below per-seat. For anything else, ask us and we will be direct about it.
No. There is no advertising in any Noctic product, on any plan, and there is no plan that removes it.
Company
Noctic™ writes the models, the accounts and the apps people actually open — and designs the silicon and the machines underneath them.
We started with one AI assistant and one school app. The interesting part turned out to be the seam between them: a single account, a single plan, one privacy model, and products that get better the moment you use another one. Everything since has been that same idea pushed further down the stack, until it reached the chip.
We believe the deep integration of hardware and software is what makes technology intuitive and beautiful. Most of it feels stitched together because it is — the model from one company, the interface from another, the device from a third, and nobody answerable for the seams between them.
So we are oriented around the whole path rather than one layer of it: the silicon, the hardware it goes into, the model, the software people live in, and one design language across all of it. Not because owning more is a virtue, but because the parts stop fighting each other only when the same people are responsible for all of them.
The honest version: it is slower, it is harder, and it leaves us with nobody else to blame. That is the trade, and we think it is the only way the result feels like one thing instead of four.
Every new surface has to earn its place by removing one somewhere else.
All model access runs server-side. It is slower to build and it is not negotiable.
Cadence is used in a real school while it's in beta. That's the feedback loop.
Clear plans, instant cancellation, no dark patterns at renewal.
"The goal isn't to make the most features. It's to make the right ones disappear."— Noctic design principle
A reasoning model and assistant, with effort tiers you choose rather than a single setting we chose for you. It is the layer the other products are built on.
A campus platform with verified rosters, real channels and a calendar that matches the timetable a student was actually handed. In beta in a working school.
A study copilot that reads only what a student approves, and plans around the schedule already in Cadence rather than asking for it again.
One identity across everything, with scoped consent for connected apps and a revoke button that actually revokes.
The machines the rest of it runs on, shaped around how the software behaves rather than around a chassis that already existed. Two desktops, and two Aebook™ laptops.
Our own chips, designed for the model they actually run rather than for a benchmark. The bottom of the stack, and the reason the top of it behaves.
Shiba began as a model and a chat window, built to be useful rather than impressive in a demo.
Cadence started because a group chat is a bad way to run a campus and everybody had quietly accepted that it was the only option.
The interesting part turned out to be the join: a single identity, a single plan, one privacy model, and products that improve the moment you open another one.
Noctic became the parent brand, and everything moved under a single ecosystem and a single policy.
Decisions live in writing so nobody needs to have been in the meeting to understand them.
A team that fits in one conversation. Every hire has to make the product better, not larger.
A real school uses the beta. What breaks there outranks what was planned for the quarter.
Privacy, minors and key handling do not get a fast lane. Nothing ships around them.
| Who runs Noctic | One person, for now, holding rather more titles than is ideal. The honest version is on Leadership. |
|---|---|
| Press and media | Announcements are in the Newsroom; assets and usage rules are on Brand. |
| Working here | Open roles, how we hire and what the trial project looks like are on Careers. |
| Privacy and data | The plain-language version is on Privacy; the binding version is the Privacy Policy. |
| Safety | How the assistant behaves by age tier, and what it will not do, is on Safety. |
| Schools | Licensing, rollout and district questions are on Education. |
| Anything else | One form, one inbox, a real person: Contact. |
What we shipped, in order.
Our ambition to design our own x86-64 processor now has a page rather than a rumour: how the chip works, how one gets manufactured, the five stages between here and a laptop part, what each stage costs, and the honest list of ways it fails. No silicon exists.
Aeon™ is labelled a concept everywhere it appears, and the lineup is now specified around shipping Intel Core Ultra parts instead of silicon that does not exist. The Aether chips remain the goal; they have simply moved to the page that admits what building them would take.
Noctic is exploring four computers — the Aeon™ and Aeon™ Neo desktops and the Aebook™ Nano and Aebook™ Pro laptops — running AXESS OS, our own Linux-based system with the Glass UI.
An AI study and planning copilot built on the school data students already keep in Cadence.
Shiba and Cadence unify under one company, one account and one ecosystem site.
OAuth 2.0 sign-in opens to first-party apps, with scoped consent and revocable access.
Six effort tiers from Economic to Ultra, visible reasoning, and Agent Mode for multi-step work.
Feed, calendar, notes, channels, DMs, reels and verified school registration. Public release NOWW!! 1, 2026.
We are a small team, so press mail goes to a person rather than an agency. Expect a reply within a working day, including a straight answer when the answer is no.
| Interviews | Available for product, education technology and privacy stories. Tell us your deadline in the first email. |
|---|---|
| Assets | Logos, product shots and screenshots on request. Usage rules are on Brand and the legal position is under Trademarks. |
| Fact checking | Send us the claim and we will confirm or correct it before you publish. This is free and quick. |
| Schools | We will not put a school or a student in front of a journalist. Any campus story goes through the school's own communications process first. |
| Embargoes | We honour them and expect the same. Everything not under embargo is already on this page. |
Useful if you are writing about us and need the description to be accurate.
| What we are | A software company. We make no hardware and sell no devices. |
|---|---|
| What we make | Shiba AI, a reasoning model and assistant; Cadence, a campus platform; Noctic Compass, a study copilot. |
| Who uses it | Individual subscribers, and schools licensing Cadence by campus. Cadence is in beta in a working school. |
| Business model | Subscriptions and school licences. No advertising in any product, on any plan. |
| How to write the name | Noctic, with the trademark symbol on first prominent use. Product names are never abbreviated. |
Privacy at Noctic
Not a setting we added later.
No AI provider key is ever shipped to a browser. Every call is proxied and rate-limited.
Birthdays, plan history and moderation records are unreadable by other users at the database level.
Connected apps receive only the scopes you approve, and you can revoke them at any time.
Encrypted mode processes locally, with screenshot and clipboard protection enabled.
Age-aware behavior across the assistant, with stricter defaults for younger accounts.
Delete your account and its content from account settings, in any product.
Each row exists because something would break without it.
| Account details | Name, email and a verified date of birth. The date of birth sets the assistant's behaviour tier; it is not shown to other users. |
|---|---|
| What you write | Conversations, notes, posts and messages. Stored so you can come back to them, and readable by you. |
| School membership | Which campus, grade or homeroom you belong to, so the right channels appear and the wrong ones do not. |
| Plan and billing | What you pay for and when it renews. Card details are handled by the payment processor and never reach us. |
| Security signals | Sign-in attempts and rate-limit counters, kept briefly, used to stop account takeover and abuse. |
| Diagnostics | Optional and aggregated. Error and performance counts with no advertising identifier attached. |
None in any product, on any plan. There is no advertising business here to compromise the rest.
We do not sell, rent or trade personal information, and we are not part of any identity graph.
Your notes, messages and assistant conversations are not used to train models.
A connected app gets the scopes you approved. New scopes require asking you again.
We do not follow you around the web, and we do not read location when the app is closed.
We do not build records about people who have never had an account with us.
Request a copy of everything held against your account, in a format you can actually open.
Fix anything wrong, including a date of birth entered incorrectly at sign-up.
Cut off any connected app from account settings. Access ends immediately, not at the next renewal.
Delete the account and its content from settings, in any product. No retention call, no exit survey.
Requests are answered within seven days and completed within thirty. Where a request comes from a parent about a student, we verify the relationship first — the detail is on Children and Students.
| Your content | Until you delete it or delete the account. We do not expire your own material to save space. |
|---|---|
| Deleted content | Removed from the live service immediately and purged from backups on the backup rotation. |
| Security logs | Kept briefly, then discarded. Long enough to investigate an incident, not long enough to be a record of you. |
| Billing records | Kept as long as tax and accounting law requires, and no longer. |
| Moderation records | Kept while the account exists, because a safety decision without a record is not reviewable. |
| School ID scans | Deleted the moment the check finishes. The card is scanned only to verify a student for the Cadence feed; we keep the yes or no and the school, never the image. |
Careers
If you like owning a product end to end, this is that.
Own the study copilot end to end: what it reads, what it suggests, and how a student says no to it. You will spend as much time on consent flows as on the interesting part, and that is the job.
Turn model capability into product behaviour that holds up in front of teenagers. Evaluation, refusal behaviour, latency budgets and the difference between a demo and something a school trusts.
Design in the browser rather than in a file. Interface work across Shiba, Cadence and this site, with a strong opinion about type, motion and what to leave out.
Sit between schools and the product. Run campus onboarding, answer the questions a district actually asks, and bring the awkward ones back to us instead of smoothing them over.
Access control, tenancy boundaries, key handling and abuse resistance on a platform full of minors. You will have the authority to block a release, and we expect you to use it.
Native clients for Cadence and Shiba. Offline behaviour, notifications that respect quiet hours, and the kind of performance work that never shows up in a screenshot.
Nothing that fits? Tell us what you'd build.
Departments
Ten teams, none of them large. Every open role above lives in one of these, and you are expected to wander into the others.
Identity, tenancy, the data layer and the background work every product sits on. If a boundary between two schools has to hold, it holds here first.
This site, the console and the dashboard. Server-rendered, fast on a school laptop, and readable without JavaScript where that is possible.
Native iOS and Android for Cadence and Shiba. Offline behaviour, notifications that respect quiet hours, and performance work that never shows up in a screenshot.
Model behaviour as a product surface: evaluation, refusals, latency budgets and the gap between a demo and something a school will trust on a Monday.
Deploys, observability, on-call and the bill. The team that finds out first, and would rather find out from a graph than from a student.
Access control, key handling, abuse resistance and the appeals route. Has the authority to block a release and is expected to use it.
Design engineering rather than handoff. Type, motion, density and a standing argument about what to leave out.
Instrumentation, experiments and honest numbers. Includes telling the rest of us when a result we liked does not survive a second look.
Between schools and the product. Campus onboarding, the questions a district actually asks, and bringing the awkward ones back to us.
Documentation, the Field Guide, error messages and release notes. Anything a user reads that is not a button is written here.
Not sure which one you belong in? Say what you'd want to own and we'll work it out.
How we work
Not a ticket queue. You take a product area, decide what it should be, and are the person who answers when it breaks.
Written by default, with a couple of hours of overlap rather than a calendar full of meetings. Decisions are written down so nobody has to have been in the room.
Cadence is in a real school while it is in beta. Feedback arrives from students the week you ship, which is uncomfortable and extremely useful.
Privacy, minors and key handling do not get a fast path. Everything else is expected to move quickly.
A short note about what you have built and what you would want to own here. No cover letter.
Forty-five minutes on your work and ours. You will speak to someone who can answer technical questions.
A scoped piece of work from something we are actually building, done on your own time and paid for. No algorithm puzzles and no unpaid weekend projects.
An answer within a week either way, with a reason. We do not leave people waiting.
| Evidence over credentials | Something you made that we can look at counts for more than where you studied. A degree is not required for any role listed here. |
|---|---|
| Comfort with ambiguity | Most problems arrive as a complaint from a real user rather than as a specification. Turning that into a decision is the skill. |
| Writing | A remote team runs on written argument. If you can explain a trade-off in a paragraph, you will do well here. |
| Judgement about minors | Every role touches a product used by teenagers. We look for people who treat that as a constraint rather than an inconvenience. |
All roles are remote and engaged as either employment or contract depending on where you are. Tell us your location early and we will be straight with you about what is possible.
Yes, where the work fits. The bar is evidence of something you built and shipped, not years of experience.
Always. It is scoped to a few hours and you keep the work regardless of the outcome.
No. Unsolicited candidate submissions are deleted unread.
Write anyway. Tell us what you would build and why it belongs here. Several of the roles above started as exactly that message.
Research
Noctic research turns reasoning, multimodality and agents into useful product behaviour—not spectacle for its own sake.
Our research programme is small and applied. We study the parts of AI that change how a product feels: how a model plans, grounds answers in real sources, uses tools, recovers from a wrong first step, and knows when a person should be brought back into the loop. One strand of it is not about models at all — Noctic Silicon is our long-range work on the processor underneath.
Same question, six budgets. The tier decides how long the model deliberates before it commits to an answer.
Six effort tiers, from Economic to Ultra. The same question can cost a fraction of a cent or run a long deliberation chain, and the user picks.
Intermediate steps are summarised into something a person can audit, rather than dumped raw or hidden entirely.
Planning, tool selection, multi-file code generation and self-correction, evaluated on whether the program actually runs.
Photographed timetables, scanned handouts, charts and panoramas. Vision that has to survive a bad phone photo in a classroom.
Models should know what they can verify, ask before consequential actions and leave a clear trail of what they changed.
Useful assistants remember the right context without turning a person’s private life into an opaque training set.
| Task completion | Did the generated program compile, run, and do the thing that was asked. Not partial credit. |
|---|---|
| Cost per solved task | Effort tiers are only useful if a cheaper tier solves most work. We track the crossover point. |
| Recovery rate | How often the model notices its own wrong turn without being told. |
| Refusal quality | Refusing the right things, and explaining why, without refusing ordinary work. |
| Real usage | Cadence runs in a real school during beta. Field failures outrank offline scores. |
| Shiba 4.5 "Parable" | Current general model. Reasoning, code, vision, voice. Six effort tiers and Agent Mode. |
|---|---|
| Cadence AI | Applied layer for education, powered by Shiba. Timetable extraction, notes, flashcards, summarisation. |
| Noctic Image | Image generation and editing, including equirectangular panorama output. |
| Noctic Voice | Low-latency speech in and out for call mode, tuned for interruption rather than monologue. |
Model behaviour is documented in the Acceptable Use Policy and constrained by the safety framework.
Hardware research
The longest-range thing we work on, and the only one measured in years rather than releases: our own x86-64 processor.
Everything above is software research, where a wrong answer costs an afternoon. Silicon is the opposite — a mistake caught late costs a mask set and a year. So this strand is deliberately slow, entirely public, and currently living in a software simulator rather than a fab. It is the most ambitious project at Noctic and the one most likely to fail, and we would rather publish the plan with the failure modes attached than imply we are further along.
Because it is not a product and will not be one for a long time. It is a question — can a small team design a useful x86-64 core — being answered in the open, one stage at a time.
A functional and cycle-approximate model in software. No RTL on an FPGA yet, no test chip, no foundry, no licence, no date. Zero parts have been taped out.
Firmware we can read, a scheduler and cores designed to agree with each other, memory decisions that belong to us, and a published errata list. Aeon™ runs Intel Core Ultra until then.
Same as anything else here: against a reference model, instruction by instruction. A core that disagrees with the specification on one edge case is a core that does not ship.
Safety
A large share of our users are minors. That is not an edge case we handle later. It is the default we design against.
One prompt, four account states. The refusal boundary never moves for harmful categories — only tone and topic latitude change.
| Under 16 | Clean language, conservative topic handling, no mature content, stricter refusal thresholds. |
|---|---|
| 16 to 17 | Mildly relaxed language. Mature and harmful categories stay closed. |
| 18 and over | Adult tone available. Illegal, harmful and exploitative categories remain refused at every age. |
| Unverified | Treated as the strictest tier until a birthday is confirmed on the account. |
Zero tolerance in every framing, including fiction and hypotheticals. Attempts are preserved, escalated and reported. See below for what that means in practice.
The assistant redirects to crisis resources and will not provide method information.
No synthesis routes, no device construction, no uplift for mass-casualty capability.
No content written to intimidate, dox or degrade a named person.
Study tools explain and quiz. They will not submit graded work on a student's behalf.
No phishing kits, no credential harvesters, no ransomware, regardless of framing.
Every post, message and generated response can be reported from where you see it.
Reports enter a queue with a full action history. Decisions are attributable to a named moderator.
Verified staff can moderate their own campus without seeing private notes or direct messages.
Suspended accounts get the reason and a route to appeal through the Field Guide.
Child exploitation
No warning. No strike count. No appeal. No exception for a first offence.
Everything else on this page is a scale. Sexual content involving minors, and any attempt to use our products to reach, groom or exploit a child, sits outside it entirely. There is no version of that conduct we manage, moderate or educate someone out of. We remove the account, we keep the evidence, and we hand it to the people whose job it is to act on it.
Access ends the moment the report is substantiated. The account cannot post, message, or reach any student while it is reviewed, and it is not restored pending an appeal because there is no appeal.
Nothing in this category is decided by an automated system alone. A trained member of staff reviews the report, and the review is prioritised above every other item in every queue.
Content, account records, sign-in history and identifiers are placed under legal hold. Deleting a message, a conversation or the account itself does not remove what has already been preserved.
We report to the national child protection body for the jurisdiction and to law enforcement, as the law where we operate requires. This is not discretionary and it does not wait for a court order.
Termination is across the whole ecosystem, not one product. Any connected application, API key and active token belonging to that account is revoked at the same time.
Attempts to come back under a new name are treated as part of the original conduct and are reported again. Deleting an account does not reset anything and never has.
We would rather someone considering this reads the list before they try it than after.
| Permanent loss of access | Every Noctic product, forever. Not a suspension, not a cooling-off period, and not something that expires quietly after a year. |
|---|---|
| No appeal | Every other enforcement decision we make can be appealed to a person. This one cannot. It is the only category where that is true, and it is deliberate. |
| Referral to law enforcement | Reports go to the police service with jurisdiction and to the national reporting body, with the preserved material attached rather than described. |
| Full cooperation with investigations | We respond to valid legal process quickly, we do not require investigators to fight us for records they are entitled to, and we have a named contact who handles nothing else. |
| Records survive the account | Material under legal hold is retained for as long as an investigation or prosecution requires, regardless of any deletion request. A deletion request is not a way to destroy evidence. |
| Civil action | Where someone has used our products to harm a child, we will pursue the remedies available to us and we will support a family or a school pursuing theirs. |
| Notification to the school | Where a student at a registered campus was targeted, the school's designated safeguarding contact is told directly and immediately, not through a monthly report. |
| No quiet settlements | We do not offer reinstatement in exchange for silence, and there is no commercial relationship large enough to change any line in this section. |
Explicit content is the end of a process, not the beginning. The conduct that leads there is itself a terminable violation, and we act on it without waiting for the point where it becomes undeniable.
An adult account attempting to open private conversation with minors it has no legitimate reason to contact.
Pushing a student towards another service specifically to continue without moderation or a record.
Asking a student to hide a conversation from parents, teachers or friends, in any wording.
Positioning an adult as the only person a student can talk to, or discouraging them from telling anyone.
Anything offered to a minor in exchange for contact, images, silence or continued attention.
Including through the assistant, including in fiction, including in a hypothetical, and including where the request is framed as a test of the system.
We do not publish how any of this is detected. Describing the mechanism in public would only help the people it exists to catch, and no amount of transparency is worth that trade.
Enforcement against an offender is the easy half. The part that matters is what happens to the student afterwards.
We assemble the record ourselves from what we already hold. A student is never asked to gather evidence, re-read what was sent to them, or repeat an account of it to us more than once.
A student who was targeted keeps their account, their notes and their standing. Being a victim is not a policy violation and is never recorded as one.
The offending account is blocked from every route to that student, including new accounts, before the student is told anything has happened.
The campus safeguarding contact is told directly, so the people who see that student every day can act in person rather than finding out later.
A parent or guardian gets a person to speak to, a clear account of what we hold, and help making the report themselves if they want to make it.
Where intimate images of a minor exist, we help the family reach the specialist services that get them taken down across the wider internet, not only from us.
Specialist help exists and is free. In Canada, Cybertip.ca and the Canadian Centre for Child Protection. In the United States, the National Center for Missing & Exploited Children. In the United Kingdom, the Internet Watch Foundation and CEOP. We will make the introduction and stay involved rather than handing over a link.
Call your local emergency services first. We cannot reach them faster than you can.
Use the report control on the message or account. Reports in this category jump every queue.
Do not confront the account, collect images, or ask a child to keep a conversation going. Preserve nothing yourself; we already hold it, and handling this material can put you at legal risk.
Reports made in good faith that turn out to be mistaken carry no consequence for the person who made them. We would rather read a hundred reports that come to nothing than miss the one that does not.
Field Guide
A redirect URL is simply the page on your own website that people land on right after they press “Continue with Noctic”. We do not give it to you — you choose it, because it is a page in your app.
How to pick one, step by step:
1. Think of the address of your app, for example https://myapp.com.
2. Add a page
that will receive the sign-in result, for example /auth/callback.
3. Put them
together: https://myapp.com/auth/callback. That is your redirect URL.
4. Open
Register an app, paste that exact address into the “Redirect URIs”
box, and save.
5. If you are still building on your own computer, also add
http://localhost:3000/auth/callback (use whatever port your app runs on).
Rules that trip people up: it must match character for character — https is not
the same as http, and a trailing slash counts. Add every address you use (local, staging,
live) as separate entries.
Go to Developers → API keys. Every app you have registered is listed there with a Copy button for the Client ID. The Client Secret is only shown once, right after you register an app — if you lost it, press Roll secret on that app and a fresh one appears.
Client ID = public, safe to put in your web page. Client Secret = private, only ever use it on your server. Never paste a secret into front-end code or a public repository.
1. Register your app and copy the Client ID and Secret.
2. Add
your redirect URL (see the article above).
3. Send people to the sign-in link — build it with the
Authorisation URL builder.
4. We send them back to
your redirect URL with ?code=shc_… in the address.
5. On your server, swap that code
for tokens — test it first with the
Token exchange tester. Then read the person's details
with the Userinfo explorer.
Scopes are the boxes the person ticks when they approve your app. identity gives you a
stable user ID. profile adds name and avatar. email adds the email address.
api allows calls on their behalf. Ask for the fewest you need — shorter consent screens
get approved more often.
PKCE is a small extra safety step for apps that cannot keep a secret — mobile apps and pure browser apps. Generate a pair with the PKCE generator, put the challenge in the sign-in link and keep the verifier in memory, then send the verifier when you exchange the code. If your app has a server that can hold the Client Secret privately, you do not need PKCE.
State is any random text you invent. You put it in the sign-in link, we hand it back untouched, and you check it matches. If it does not match, someone else started that sign-in and you should ignore it.
Access tokens last one hour. Refresh tokens last thirty days and are replaced each time you use one.
Paste any token into the Token inspector to see its
exact expiry. To refresh, call the token endpoint again with grant_type=refresh_token.
The address in your sign-in link is not identical to one saved on your app. Copy the address from the
error, open API keys, and paste it in exactly. Check for:
http vs https, www vs no www, a different port, a
trailing slash, or capital letters.
The Client ID or Secret is wrong, has extra spaces, or belongs to a different app. Re-copy both from API keys. If the secret was ever shared, roll it.
Authorisation codes are single-use and expire after sixty seconds. Exchange the code immediately on your server, and never reuse one. Refreshing the page after sign-in also reuses the code — that is the most common cause.
Almost always one of three things: you are offline, an ad blocker is blocking the request, or you are calling from a page that is not allowed. Try again in a normal browser tab, and if it persists send us the exact request through Contact.
We include a header X-Noctic-Signature: sha256=…. Take the raw request body, sign it with
your signing secret using HMAC-SHA256, and compare. The
Webhook signature tool produces the exact value so
you can check your code matches.
Sixty sign-in requests per minute per app and six hundred API calls per minute. If you go over you
receive HTTP 429 with a Retry-After header. Wait that many seconds and try again.
Yes. Register the app, add a localhost redirect URL, and sign in with your own Noctic
Account. Nothing is public until you share the link.
One sign-in that works across every product we make. It carries your name, avatar, plan, verification status and the permissions you have granted to connected apps. Create it once at Sign in.
Open the sign-in page, enter your email and request a reset link. The link expires after one hour and can only be used once. If it does not arrive within a few minutes, check spam and confirm the address is the one on the account.
At least eight characters, with an uppercase letter, a number and a special character. We also check the password against known breach corpora using a privacy-preserving hash prefix, so a password that has already leaked cannot be used here.
Open Noctic Account. Editing your email sends a confirmation link to the new address; the change only applies once you click it, so the old address keeps working until then.
Noctic Account lists every app you granted access to, what it can see, and a Revoke button. Revoking is instant and its tokens stop working straight away.
Account settings in any product has a delete option. Deletion removes your profile, posts, notes and generated content across the ecosystem. It cannot be undone, and it completes within thirty days.
Usually the account exists from another Noctic product — one account covers all of them. Use “Forgot password” on the sign-in page to take control of it. If that email is not yours, tell us through Contact.
Free is zero. Noctic Plus is four hundred and fifty dollars a year and Noctic Pro is eight hundred and ninety-nine, both covering Shiba, Cadence, Momentum and Compass. Drop an app you will not use and the price drops with it. See Pricing to build yours.
Access is revoked immediately rather than silently continued at a lower tier. Update the card and the plan restores on the next successful charge.
Cancel from billing settings. Cancellation is immediate at the end of the current period, with no retention flow and no cancellation fee.
Invoices are in billing settings and are emailed after each charge. For a refund, write to us through Contact within fourteen days of the charge and tell us what went wrong.
Treats are the daily usage allowance on the Free tier. Higher effort tiers consume more treats per request, from a quarter of the base cost at Economic up to eight times at Ultra. Treats reset daily.
They control how long the model deliberates before answering. Economic is near-instant and cheap. Ultra runs a long reasoning chain for hard problems. Most everyday questions are well served at Low or Medium.
Yes. The thought process is summarised and shown above the answer. It is a summary, not the raw chain, because raw chains are long and often misleading out of context.
Agent mode lets Shiba plan a task, run several steps in a row and check its own work before answering. Use it for long jobs like building a page or reworking a document; use normal chat for quick questions.
Drop the effort tier one step, shorten very long attachments, and check Service status. If a specific prompt always fails, send it to us through Contact and we will look at that request.
Open Cadence, choose your campus, and scan a genuine student or staff identification card. The scan is checked for authenticity before the school is created. Fabricated cards are rejected and the attempt is logged.
Take a photograph of the printed schedule, or upload a PDF, from the calendar screen. The extraction runs server-side and writes real calendar entries you can then edit.
Make sure the whole page is in frame, the text is in focus, and the file is under ten megabytes. Photographs of screens often blur — a PDF works best. Try again, then contact us with the file if it still fails.
Verification is free. Scan a valid identification card during school registration. Verification earned in one product is recognised everywhere in the ecosystem.
A repost shows a small “you reposted” header on the original post and is visible to your followers. School and grade channels are joined automatically once your school is confirmed, and you can leave any channel from feed settings.
Open the download page in Cadence. Android gets an APK — your phone will warn that it is not from a store, which is expected for a direct download. iPhone uses Add to Home Screen from the share menu.
Register an application to receive a client identifier, a secret and your redirect URIs, then run a standard OAuth 2.0 authorisation code exchange. Full steps are on the Developers page.
Identity, profile, email and api. Each is approved separately by the user on the consent screen and can be revoked at any time from account settings.
We do not use private notes, direct messages or encrypted conversations for training. See the Privacy Policy for the full description of what we process and why.
Use the report control on the post, message or response. Reports enter a moderation queue with an audit trail. Urgent safety matters can also be raised through Contact.
Ask through Contact choosing the privacy topic. We reply with a machine-readable export within thirty days, at no cost.
Send the details through Contact with reproduction steps. We acknowledge reports and do not pursue researchers acting in good faith. Details are on the Security page.
Do these in order: reload the page, check Service status, sign out and back in, then try a private window with extensions off. If it is still broken, send us the page address and a screenshot through Contact.
Keyboard
Noctic reads which system you are on and shows that system's keys. You are on your device, so the modifier below is the modifier key. Open the full list at any time with .
Jump to any page, or run a command like switching the colour scheme.
Works anywhere you are not typing into a field.
A panel over the page, with the keys written for your system.
Palette, menus, date pickers, confirmations — all of it.
Press and then one more key. You have about a second and a half for the second press.
Because it would not work. Your operating system claims those keys before a web page is told about them, so a shortcut built on either would silently do nothing. Off the Mac we use Control instead, which a browser tab can actually receive.
We read what your browser reports. A browser in a compatibility mode, or a remote desktop session, can report the host rather than the machine in front of you. Everything still works; only the labels are wrong.
We deliberately avoided the combinations browsers reserve for tabs, windows, bookmarks and printing. is claimed by some address bars, and we take priority on this site the same way other web apps do.
The single-key ones never fire while you are typing in a field, which is the case people actually trip over. If they still get in your way, tell us at contact and we will add a switch to Settings.
The palette is a labelled combobox with a listbox of results, the panel is a modal dialogue, and focus returns to wherever you were when either closes. More in Accessibility.
Checked live, from your browser, every thirty seconds.
Rows marked with a timing were measured from this browser a moment ago, so they reflect the path between you and us — a slow network of your own will show here too. Rows marked Reported by Noctic come from us: an endpoint answering is not proof that the feature behind it works, so a declared incident always outranks a probe. Incidents are posted here first and summarised afterwards in the Newsroom.
| Operational | Working normally. Ordinary variation in speed is not an incident and we will not post about it. |
|---|---|
| Degraded | Usable but slower or less reliable than it should be. Some requests fail and succeed on retry. |
| Partial outage | One feature or one region is down while the rest of the service continues. |
| Major outage | A core service is unavailable to most people. Posted within fifteen minutes of us confirming it. |
| Maintenance | Planned work with a start and end time, announced at least three days ahead. |
A first post as soon as we have confirmed the problem, even when we do not yet know the cause. Silence is worse than an incomplete update.
Regular updates while the incident is open, whether or not anything has changed.
Only once it is genuinely fixed for everyone, not once it looks better on our side.
Anything that reached a major outage gets a plain-language summary in the Newsroom: what broke, who it affected, and what changed so it does not happen again.
Planned work avoids the school day in the regions where Cadence is in use. Term start is frozen entirely.
At least three days' notice here, and a note in the campus channel where a school is affected.
Where we can, the calendar and existing posts stay readable while the rest is being worked on.
School administrators hear from their named contact rather than finding out from this page.
Seeing a problem that is not listed here? Tell us through Support — a report from one person is often how we find out.
Small team, real replies.
Account, billing and product problems. Start in the Field Guide, then write to support at noctic.
District licensing, rollout and staff training for Cadence and Compass. Write to education at noctic.
Vulnerability reports and coordinated disclosure. Write to security at noctic. See Security.
Access, correction and deletion requests under applicable law. Write to privacy at noctic.
Trademark, copyright and law-enforcement requests. Write to legal at noctic. See Legal.
Interviews, briefings and brand assets. Write to press at noctic. See Brand.
One form, one inbox, a real person. We usually answer within one working day. You get a copy by email.
Faster answers for common questions are in the Field Guide. Live incidents are posted on Service status.
| Support and billing | One working day, usually the same day. Refund decisions are made in the first reply. |
|---|---|
| Schools and districts | One working day, from the person who knows your campus rather than a general queue. |
| Privacy requests | Acknowledged within seven days, completed within thirty. |
| Security disclosure | Same day, including weekends. |
| Press | One working day. Tell us your deadline in the first email and we will work to it. |
| Anything involving a student's safety | Immediately, ahead of everything else. |
We answer in English and French. There is no phone queue and no chatbot in front of the inbox.
What you did, what you expected, and what happened instead. Three lines saves three emails.
Browser or app, device, and roughly when it happened. The exact wording of any error message helps most.
No passwords, no full API keys, no session tokens. We will never ask for them, and anyone who does is not us.
Screenshots from Cadence usually contain students. Cover names and faces before sending.
Report in good faith and we will not threaten you for it. We reply the same day, keep you updated while we fix it, and credit you publicly if you want that.
The mark is a single drop. Keep it that way.
| Name | Noctic, always capitalised. Use the trademark symbol on first prominent use: Noctic™. |
|---|---|
| Products | Shiba AI, Cadence, Noctic Compass, Noctic Account. Never hyphenate or abbreviate them. |
| Clear space | Leave at least the height of the mark as empty space on every side. |
| Colour | Black on light surfaces, white on dark surfaces. No gradients, no shadows, no outlines added to the mark. |
| Do not | Recolour, rotate, stretch, animate, place the mark inside another shape, or lock it up with a third-party logo. |
| Endorsement | Do not use our marks in a way that suggests partnership, sponsorship or approval without written permission. |
Most brand mistakes are typographic, not graphic.
| Correct | Noctic. Shiba AI. Cadence. Noctic Compass. Noctic Account. Continue with Noctic. |
|---|---|
| Incorrect | NOCTIC, noctic, Noctic.ai, Noctic AI, Shiba AI™ on every mention, Cadence App, Compass by Noctic. |
| Trademark symbol | Once, on the first prominent mention in a document. Not in headlines, and not on every repeat. |
| As a verb or noun | Our names are adjectives. Write "the Cadence calendar", not "Cadence it" or "send me a Cadence". |
| Possessives and plurals | Avoid both. Write "the Shiba AI assistant" rather than "Shiba AI's assistant" or "Shibas". |
| Translation | Product names are not translated or transliterated. They stay as written in every language. |
Never below sixteen pixels on screen or five millimetres in print. Below that the drop stops reading as a drop.
At least the full height of the mark on every side, kept free of type, rules and other logos.
Solid, quiet surfaces. Not over busy photography, not over a gradient, not over another logo.
Black on light, white on dark. No brand colour version of the mark exists, so please do not invent one.
Use the file we supply. Do not trace it, re-letter it, or rebuild it from a screenshot.
Do not place the mark beside your own logo as a single unit. Separate them, or use text instead.
| Ink | #1D1D1F on light surfaces. #F5F5F7 on dark. Pure black is reserved for full-bleed dark sections. |
|---|---|
| Accent | #0071E3, used for actions and links only. It is not a decorative colour and not a background. |
| Surfaces | #FFFFFF and #F5F5F7 in light appearance; #000000 and #101010 in dark. |
| Typeface | The system sans on each platform. If you need a substitute, use Helvetica or Arial, never a display serif. |
| Setting | Sentence case everywhere, tight letter-spacing on headlines, and no all-caps product names. |
Take the screenshot from a current build. Do not mock up an interface and present it as ours.
Cropping and scaling are fine. Changing labels, colours or figures inside the screenshot is not.
Screens from Cadence often contain students. Remove names and faces before publishing anything.
Logos, product shots and fact-checking go through the press contact on Contact.
Everything else, ask. Requests go to the press contact on Contact and are usually answered within a few days. The legal position is set out under Trademarks.
Legal
Everything that governs your use of Noctic, in one place.
The agreement between you and Noctic covering accounts, plans, content and liability.
What we collect, why we collect it, how long we keep it and the rights you hold over it.
The small number of storage keys we set, and what each one does.
What you may not do with our products, and what happens when someone does it.
How the system is built and how to report a vulnerability responsibly.
Our commitment, the standard we target and how to tell us where we fall short.
Additional protections that apply to accounts belonging to minors.
The marks we own and the limited ways they may be used.
How to submit an infringement notice and how to counter-notify.
| You use Shiba or Cadence | The Terms of Service and the Acceptable Use Policy govern your account. The Privacy Policy covers what we hold. |
|---|---|
| You are under eighteen | Everything above applies, and Children and Students adds protections on top. Where the two differ, the stricter one wins. |
| You are a school | Your campus agreement sits alongside these policies. Children and Students describes what staff can and cannot see. |
| You build on the API | The Terms, the Acceptable Use Policy and the platform rules under Platform apply to your app as well as your account. |
| You are writing about us | Trademarks for the legal position, Brand for presentation. |
| You own content we host | The notice and counter-notice process is on the Copyright page. |
Every policy carries the date it last changed at the top. Nothing is edited quietly.
Material changes are announced at least thirty days before they take effect.
If you do not accept a change, delete the account before it takes effect and nothing new applies to you.
We require valid legal process for user data. We tell the affected person unless we are legally prohibited from doing so, we read every request for scope and push back on the ones that are too broad, and we do not provide bulk or standing access to anyone.
Emergencies involving a risk to life are handled immediately and reviewed afterwards. Requests go to the legal contact on Contact.
Last updated August 8, 2026
These terms govern your use of Noctic™ products, including Shiba AI, Cadence, Noctic Compass and the Noctic Account. By creating an account or using a product, you accept them. If you do not accept them, do not use the products.
You must be at least thirteen years old to create an account, and old enough to consent to data processing where you live. You are responsible for the security of your credentials and for everything done through your account. Provide accurate information, including your date of birth, because product behaviour depends on it. We may suspend or close accounts created with false information.
You keep ownership of what you write, upload and generate. You grant us the limited licence needed to store, transmit, display and process that content in order to operate the products you asked for. That licence ends when you delete the content, apart from copies retained in backups for a limited period or where retention is legally required.
Subject to these terms, you own the output the models produce for you. Output may be inaccurate, may resemble output given to others, and must not be relied on as professional, legal, medical or financial advice. You are responsible for reviewing output before you use it, publish it, or submit it anywhere it matters.
Your use must comply with the Acceptable Use Policy. We may remove content, restrict features, or suspend accounts that breach it, and we will tell you the reason where we are permitted to.
Paid plans renew on a yearly cycle until cancelled. A plan covers the applications you selected when you bought it; applications you did not select remain on their free tier. Prices are shown before purchase and may change with notice ahead of a renewal. If a payment fails, access to paid features is revoked immediately rather than silently downgraded. Cancellation stops the next renewal and takes effect at the end of the paid period. Campus agreements are governed by their own ordering document.
Free accounts receive a daily allowance. We apply rate limits, abuse detection and minimum account-age rules to prevent automated farming of that allowance. Circumventing these controls is a breach of these terms.
Where a school or organisation licenses a product for you, an administrator may manage your access, moderate shared spaces, and see participation data. Administrators cannot read private notes or direct messages. Their agreement with us governs where it conflicts with these terms.
Applications that use Continue with Noctic receive only the scopes you approve. Those applications are operated by their developers, not by us, and their handling of your data is governed by their own terms. Revoke access at any time from account settings.
We keep all rights in the products, models, software, designs and marks. Nothing here transfers those rights to you. See Trademarks for permitted use of our names and logo.
Products marked beta or preview, including Cadence before its public release now, are provided as they are. They may change, break or be withdrawn, and they carry no availability commitment.
To the fullest extent permitted by law, the products are provided without warranties of any kind, and our aggregate liability is limited to the amount you paid us in the twelve months before the claim arose. Nothing here limits liability that cannot lawfully be limited, including for death, personal injury or fraud.
You may stop using the products and delete your account at any time. We may suspend or terminate access for breach of these terms, for legal reasons, or to protect other users. Where we terminate without cause, we refund the unused portion of a paid period.
We may update these terms. Material changes are announced before they take effect, and continued use afterwards means acceptance. The date at the top always reflects the current version.
Questions about these terms go to the legal contact listed on the Contact page.
Last updated August 8, 2026
This policy explains what Noctic™ collects, why, how long we keep it, and what you can do about it. It applies to Shiba AI, Cadence, Noctic Compass, the Noctic Account and this website.
We do not use private notes, direct messages, or conversations held in encrypted mode to train or fine-tune models. Where we use any content to improve quality, it is de-identified first, and you can opt out from account settings.
A school identification card is collected for one purpose: to confirm that the holder is a currently enrolled student, so that a verified account can take part in the Cadence social feed. The scan is read by the verification model and then deleted immediately once the check completes — whether it passed or failed. We keep the outcome, the school it named and the date, and nothing else.
The image is never shown to other users, never shown to school staff, never used to train a model, and never retained as a record of identity. There is no archive of student cards to request, to leak or to be compelled to hand over, because after the scan there is nothing left to hand over.
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We share it only with processors who run infrastructure, payment and model services on our behalf under contract, with applications you explicitly authorise through Continue with Noctic, and with authorities where the law compels it. Where a school licenses a product, administrators see participation and moderation data, never private notes or direct messages.
Sensitive fields, including date of birth, plan history and moderation records, are unreadable by other users at the database level rather than merely hidden in the interface. Model provider keys never reach a browser; every model call is proxied server-side and rate limited.
Depending on where you live, you may request access, correction, deletion, a portable copy, restriction of processing, or object to processing based on legitimate interests. Deletion is available directly in account settings. Other requests go to the privacy contact on the Contact page, and we respond within thirty days. You may also complain to your local supervisory authority.
Our infrastructure and processors may be located outside your country. Where that happens we rely on recognised transfer mechanisms and contractual safeguards.
Accounts belonging to minors receive additional protections described in Children and Students. We do not knowingly create accounts for anyone under thirteen, and we delete them when we discover them.
Material changes are announced before they take effect. The date at the top always reflects the current version.
Last updated August 8, 2026
We use a deliberately small number of cookies and browser storage keys. We run no advertising trackers and no cross-site profiling.
Strictly necessary keys cannot be disabled without breaking sign-in. Everything else can be cleared from your browser at any time, and optional diagnostics can be turned off in account settings.
| Session token | Ends when you sign out or when the session expires. Refreshed while you are active so you are not signed out mid-task. |
|---|---|
| Appearance and language | Stored on the device until you clear it. Never sent to us, and never used to identify you. |
| Security and rate limiting | Short-lived. Exists to stop automated abuse of sign-in and the API. |
| Diagnostics | Optional, aggregated, and off in any region that requires consent before it is on. |
Some preferences are kept in local storage rather than in a cookie: your appearance choice, your language, and a translation cache that stops the same phrase being sent for translation twice. These stay on your device. Clearing site data removes them.
We set no advertising cookies and embed no advertising trackers. We do not run cross-site profiling and we do not participate in data co-operatives or identity graphs. Where a page loads something from another service, it is because that service is doing work you asked for, such as processing a payment.
We honour the Global Privacy Control signal where your browser sends it. Because we do not sell or share personal information for advertising, the practical effect is to turn off optional diagnostics.
In regions that require consent before non-essential storage, optional diagnostics stay off until you turn them on, and nothing beyond the strictly necessary keys is set before that. Your choice is remembered per device and can be changed at any time in account settings.
Every browser can block or clear cookies for a single site. Blocking the strictly necessary keys will stop sign-in from working, which is a limitation of how sessions work rather than a choice we made. Nothing else breaks.
If we add a cookie or a storage key, this page is updated before it ships, and the date at the top changes. Material changes are also noted in the Newsroom.
Last updated August 8, 2026
This policy applies to every Noctic™ product and to anything built on our interfaces. It is written short on purpose.
Depending on severity we may remove content, restrict features, suspend the account, or terminate it. Serious matters, including material involving minors, are escalated to the appropriate authorities. Suspended users are told the reason and may appeal through the Field Guide.
| A mistake | A refusal and an explanation. Most first contacts with this policy end here and nothing happens to the account. |
|---|---|
| Repeated attempts | A warning naming the rule, and the feature involved may be restricted while it is reviewed. |
| Deliberate misuse | Suspension, with the reason stated and an appeal available. |
| Harm to a person | Immediate termination, no warning, and referral where the law requires it. |
| Anything involving minors | Immediate permanent termination across every product, evidence preserved under legal hold, and a report to law enforcement and the national child protection body. No warning, no threshold for a first offence, and no appeal. The full position is on Safety. |
An appeal is read by a person, not by the system that made the decision. Tell us what you were doing and why you believe the decision was wrong. We answer within five working days and we will say plainly if the answer is no. Decisions involving child safety are not appealable.
Conduct inside a campus is moderated by that school's own staff under the school's policy. This document sets the outer boundary that applies everywhere regardless of what a campus permits, and we act on it whether or not the school does.
An application built on our interfaces is responsible for what its users do through it. Apps that systematically enable conduct on this list lose access, and apps that ship a client secret in front-end code are suspended until it is rotated. The platform rules are on Platform.
Some enforcement starts automatically because volume requires it. Any action that suspends or terminates an account is reviewed by a person before it stands, and any action taken in error is reversed with the account restored to where it was.
Report an account, a post or a message through the product where you found it, or write to us through Contact. Reports about the safety of a student are handled ahead of everything else in the queue. If you believe someone is in immediate danger, contact your local emergency services first — we cannot reach them faster than you can.
This policy can change as products change. The date at the top moves whenever it does, and material changes are announced in the Newsroom before they take effect.
Last updated August 8, 2026
Send reproduction steps, affected endpoints and impact to the security contact on the Contact page. Please give us reasonable time to fix an issue before disclosing it, avoid accessing other people's data, and do not run denial-of-service or automated scanning against production. We will not pursue researchers acting in good faith under these conditions.
Missing best-practice headers with no demonstrated impact, self-inflicted issues requiring a compromised device, social engineering of our staff, and reports produced solely by automated scanners without a working proof of concept.
| First reply | Same day, including weekends, from a person rather than an automatic acknowledgement. |
|---|---|
| Assessment | Within three working days we confirm whether we could reproduce it and how we are rating the impact. |
| Critical issues | Mitigated immediately, ahead of anything else in progress. |
| Updates | You hear from us while it is open, not only when it is closed. |
| Credit | Public thanks if you want it, silence if you would rather not be named. |
| Good faith | We will not pursue legal action against researchers who follow the conditions above. |
Cadence holds data belonging to minors. Please do not test against real school accounts, real student data or a live campus. If a vulnerability can only be demonstrated that way, tell us what you believe is possible and we will reproduce it ourselves on a test campus rather than asking you to.
In the event of a breach affecting personal data we notify affected people directly and without delay, notify the relevant supervisory authorities within the period the law requires, tell the schools involved before we tell anyone else, and publish a plain-language account in the Newsroom once people have been informed. We would rather publish an uncomfortable summary than a vague one.
Last updated August 8, 2026
We target conformance with the Web Content Accessibility Guidelines, version 2.2, at level AA, across every product we ship.
Some dense data views and the panorama viewer are not yet fully operable by keyboard alone. Work on those is in progress.
If something is unusable, write to us through Contact with the page and the assistive technology you use. Accessibility reports are treated as defects, not feature requests.
Automated checks catch a minority of real problems, so every release is also driven by hand. We test with VoiceOver on macOS and iOS, NVDA on Windows, TalkBack on Android, keyboard-only navigation in each supported browser, and both appearance modes at two hundred per cent zoom.
| This site | Fully keyboard operable, with a visible focus ring on every control and headings that describe the page rather than decorate it. |
|---|---|
| Shiba | Conversations are a semantic list, streamed replies are announced without interrupting, and every control has a text label as well as an icon. Reasoning output can be collapsed entirely. |
| Cadence | Feed, channels and calendar are navigable by keyboard and by heading. Calendar entries carry full dates in text so a screen reader never has to interpret a grid position. |
| Compass | Study plans are readable as ordinary text, not only as a chart, and every suggestion states its reasoning in words. |
Cadence is used by whole campuses, which means it is used by students with formal accommodations. If a student's plan requires a change we do not currently support, write to us through the school. We treat that as a defect on the same footing as any other, and we will tell you honestly whether it is weeks or months away.
| Acknowledgement | Within two working days, from a person rather than an automatic reply. |
|---|---|
| Assessment | Within ten working days we tell you what we found, whether it is a defect, and what happens next. |
| Blocking problems | Anything that makes a core task impossible is fixed ahead of feature work. |
| Everything else | Scheduled, with the date shared with you rather than kept internally. |
This list is kept current. We would rather publish an honest gap than claim conformance we have not earned.
Last updated August 8, 2026
Cadence is used in schools, so most of the people in it are minors. These additional protections apply to those accounts.
Accounts require a minimum age of thirteen. We do not knowingly serve anyone younger, and we delete such accounts when we find them. Where local law sets a higher age of consent, that age applies.
Assistant language and topic handling are tied to the verified date of birth. Unverified accounts are treated as the strictest tier. See Safety for the tiers.
Staff and administrators see channel activity, moderation reports and participation. They do not see private notes, direct messages or assistant conversations.
We do not build advertising profiles of students, and we do not show advertising in any product.
A parent or guardian may request access to, correction of, or deletion of a minor's data through the privacy contact on the Contact page. We verify the relationship before acting.
Send the student's full name, the school, the account email if you know it, and what you are asking for. We reply within seven days and complete most requests within thirty. If we cannot verify that you are the parent or guardian of that student, we will say so rather than release anything.
A student account is any account created through a registered school, or any account whose verified date of birth places the holder under the age of majority where they live. Staff accounts at the same school are not student accounts, even when a teacher is in the same channel.
Where this page and the Privacy Policy differ, the stricter of the two applies to student accounts.
| Identity | Name, school, grade or homeroom, and a verified date of birth used to set the behaviour tier. |
|---|---|
| School activity | Channel posts, replies, bulletin entries and anything else published to a group at the school. |
| Private content | Notes, direct messages and assistant conversations. Held for the student, not for the school. |
| Calendar | The school year plus whatever the student adds or imports from a photographed timetable. |
| Safety records | Reports filed, reports received, and actions taken by moderators, with the reason recorded. |
| Identification | The result of the student ID check and the school it named. The scan itself is deleted as soon as the check finishes, so no card image is held against a student account. |
Assistant tone, topic handling and refusals are set by the verified date of birth rather than by a self-declared age. An account without a verified date of birth is treated as the strictest tier until it is verified. The tiers themselves are described on the Safety page.
The assistant will not help with anything that would put a student at risk, and it does not pretend to be a counsellor. Where a conversation suggests a student is in danger, it points to real help rather than continuing the conversation.
Direct messages and private notes are not visible to staff, administrators or other students. Schools cannot request bulk access to them, and there is no administrator view that exposes them. The exception is a specific message reported for review, which a moderator sees only in the context of that report.
Any student can report a post, a message or an account. Reports go to a queue staffed by the school's own moderators, with every action logged and attributable. A student who is actioned is told what happened and can ask for it to be reviewed again.
Reporting is not anonymous to us, because a reporting system that cannot be audited is a system that gets abused. It is anonymous to the person being reported.
There is no infinite feed, no streak mechanic and no notification designed to pull a student back. Quiet hours are on by default for student accounts, and channels a student is not part of cannot notify them.
Leaving a school removes access to that school's channels and calendar immediately. The account itself survives — notes, direct messages and assistant history belong to the student, not the campus. Deleting the account removes all of it. School-owned content such as a channel announcement written by staff stays with the school.
Where local law sets a higher minimum age, a stronger consent requirement or a shorter retention limit than this page describes, the local rule applies to accounts in that region. This includes the student privacy and parental consent regimes in the United States, Canada, the United Kingdom and the European Economic Area.
This is the one part of our rules that has no scale, no warning and no appeal. An account used to reach, groom, sexualise or exploit a child is terminated permanently across every Noctic product, its content and records are placed under legal hold, and it is reported to law enforcement and to the national child protection body for the jurisdiction, as the law where we operate requires.
Deleting the account does not undo any of that. Material already preserved stays preserved, a deletion request is not a route to destroying evidence, and an attempt to return under a new name is treated as part of the original conduct and reported again.
Waiting for explicit material means waiting until the harm has already been done. We act on the pattern that leads there: an adult seeking private contact with students, pushing a conversation onto another service to escape moderation, asking a child to keep something secret from parents or teachers, offering gifts or money for contact or images, or positioning themselves as the only person a student can talk to. Each of those is a terminable violation on its own.
We do not publish how this is detected. Explaining the mechanism would help the people it exists to catch, and that is not a trade we are willing to make for the sake of transparency.
We respond to valid legal process in these cases quickly and without argument, and we do not make investigators fight us for records they are entitled to. Where a family or a school pursues civil action, we will support it, and we will pursue the remedies available to us. There is no commercial relationship, school agreement or account size that changes any of this.
Enforcement against an offender is the straightforward half. What happens to the child afterwards matters more, and it is where we put the effort.
Free specialist help exists: Cybertip.ca and the Canadian Centre for Child Protection in Canada, the National Center for Missing & Exploited Children in the United States, and the Internet Watch Foundation and CEOP in the United Kingdom. We make the introduction and stay involved rather than handing over a link.
If a child is in immediate danger, contact your local emergency services first — we cannot reach them faster than you can. Otherwise use the report control in the product, or write to us through Contact marked urgent. Reports in this category are monitored outside working hours and jump every queue.
Do not confront the account, collect images, or encourage a child to keep the conversation going. Handling that material can put you at legal risk, and we already hold what is needed. A report made in good faith that turns out to be mistaken carries no consequence for the person who made it. We would rather read a hundred reports that come to nothing than miss the one that does not.
Anything on this page can be asked about directly through Contact. Questions from parents are answered by a person, not a form response. The wider enforcement picture is on the Safety page.
Last updated September 14, 2026
Noctic™, the Noctic drop mark, Shiba AI, Cadence, Cadence AI, Noctic Compass, Noctic Account and Aeon™ — including Aeon™ Neo — and Aebook™ — including Aebook™ Nano and Aebook™ Pro — are trademarks of Noctic. All rights are reserved.
Requests for permission go to the legal contact on the Contact page.
You may say what your product does with ours. You may not name your product after ours. "Timetable sync for Cadence" is fine. "CadenceSync" is not, and neither is a name that merely rhymes closely enough that people will assume a connection.
The same applies to domain names, subdomains, application identifiers, package names, social handles and repository names. A descriptive phrase is acceptable; a name that reads as ours is not.
A community project that works with our products can say so plainly in its description and documentation. It may not use our marks in its own name, its logo or its package identifier, and it should state clearly that it is unaffiliated.
Journalists, researchers and educators may use our names to refer to us without asking, provided the use is accurate and does not suggest we participated. The presentation rules are on Brand.
If you find our marks being used to impersonate us, particularly on a sign-in page or in something aimed at students, tell us through Contact with a link and a screenshot. Impersonation that puts minors at risk is escalated the day we receive it.
We would rather correct a misunderstanding than start a dispute, and most matters end with a short email. Permission granted under this page can be withdrawn in writing, and no permission is implied by the absence of an objection.
Last updated August 8, 2026
We respond to valid notices of claimed copyright infringement and terminate the accounts of repeat infringers.
Send the following to the legal contact on the Contact page:
If your material was removed in error, you may send a counter-notice with the same contact details, identification of the removed material, and a statement under penalty of perjury that the removal resulted from mistake or misidentification. We may restore the material after the statutory waiting period unless the original complainant files an action.
Knowingly filing a false notice carries liability. We keep a record of every notice received.
| Acknowledgement | Within two working days, confirming what we received and whether anything is missing. |
|---|---|
| Assessment | We check the notice is complete. An incomplete notice is returned with the missing element named rather than ignored. |
| Action | Valid notices result in removal or disabling of access to the material, usually within five working days. |
| Notification | The person who posted it is told what was removed and why, and is given a copy of the notice. |
| Counter-notice | If one arrives, we forward it to you and the statutory waiting period begins. |
We keep a record of valid notices against each account. An account that accumulates repeated valid notices is terminated, and the count is not reset by deleting and recreating the account.
A notice about material generated by one of our models should identify the specific output and where it appears, in the same way as any other notice. We investigate these seriously and will tell you what we find, including when the honest answer is that the output does not reproduce the work you have identified.
Consider whether the use might be permitted. Quotation, commentary, criticism, news reporting and teaching are lawful in many places, and a notice filed against clearly lawful use may itself carry liability. If you are unsure, take advice — we cannot give you legal advice about your own notice.
The model
The reasoning model underneath everything we make. It thinks before it answers, shows the shape of that thinking, and stops when it is not sure.
Parable is a single model with an adjustable amount of deliberation, not a family of models you have to choose between. The same weights answer a one-line question and a week-long project; what changes is how long it is allowed to think.
Most systems make you guess which model fits your question. Parable takes the effort as a parameter instead. Ask for less and you get an answer in a second; ask for more and it will plan, check itself and revise before it replies.
| Economic | Reflex answers. Definitions, reformatting, short translations, tidying a sentence. No planning stage at all — under a second in most cases. |
|---|---|
| Standard | The default. One planning pass, then an answer. Good for ordinary questions, short code, summarising a document you have just pasted in. |
| Extended | Plans, drafts, then reads its own draft back before answering. Where most real work belongs — essays, multi-file changes, arguments with more than one moving part. |
| Deep | Several independent attempts, compared against each other. Noticeably better on maths, proofs and anything where a subtle error early ruins everything after it. |
| Research | Long-horizon work with tool use throughout. Reads, searches, runs code, keeps notes, and reports what it could not establish as well as what it could. |
| Ultra | Everything Deep does, run wider and for longer, with an explicit adversarial pass looking for reasons the answer is wrong. Slow and expensive on purpose. |
Effort is a ceiling, not a quota. Ask for Ultra on a question that needs Standard and Parable will stop early rather than pad the answer out to justify the setting.
Question, attachments, conversation history and whatever memory you have allowed it, in one pass.
Whether to search, run code, open a file, or simply answer. Tool use is a decision, not a reflex.
You can watch the plan and the steps. Nothing important happens in a part you cannot see.
At Extended and above it reads its own draft looking for the mistake it is most likely to have made.
Trained so that "I am not sure" tracks actual accuracy. When Parable hedges, the hedge means something — it is not politeness.
When it has searched, claims carry the source that produced them. A claim with no source attached is a claim from the model's own weights, and it says so.
Missing information produces a question, not an invented value. This is the single most common complaint about assistants and the thing we spend the most effort on.
Quality at 900,000 tokens is close to quality at 9,000. Instructions given at the start still hold at the end, which is the part most long-context claims quietly skip.
Published because a model card that only lists strengths is marketing. These are the failure modes we know about and have not fixed.
It will reason correctly about the method and then slip a digit. At Deep and above it reaches for a calculator instead, which is the right instinct but means the raw model is weaker than it looks.
Anything after the training cut-off only exists if it searches for it. Without search, it will sometimes answer confidently about a world that has moved on.
Reliable up to a handful of objects and unreliable past that. It reads text in images well and counts poorly, which is an odd combination but a real one.
It cannot tell the difference between something you never mentioned and something it has forgotten. If memory is off, it will not notice the gap.
Push back hard enough on a correct answer and it will sometimes fold. We test for this and it is better than 4.0, but it is not gone.
It holds a plot for a few thousand words and then starts contradicting itself on details it established earlier. Useful for drafting, not for finishing.
The assistant. Every effort tier, Agent Mode, artifacts, voice and memory.
Answers in channels, turns a photographed timetable into a calendar, moderates at the edges.
Plans the term and tutors the specific gap, at Extended effort by default.
Through the api scope, counted against the user's plan rather than yours. See the
developer section.
Noctic Education
Less time on the administration around teaching, and a straight answer about what your students are actually doing with AI.
We did not build this by imagining a classroom. Cadence started at one school, with teachers telling us which parts of the week were wasted. Most of what follows came from those conversations rather than from a product plan.
Post to a class, a grade or the whole school. It lands in the feed, in the calendar if it has a date, and as a notification only for the people it concerns.
Photograph the printed timetable. Cadence reads it into a real calendar, including rotations and week A/B patterns, and asks about anything ambiguous rather than guessing.
Paste one key into the site you already post to. Slide decks, notes and handouts arrive in Cadence under your class, and the tutoring quotes your slides instead of guessing at the syllabus. Get a teacher key.
Optional, and never final. Parable drafts feedback against your rubric and flags the specific line it is responding to. You edit and release; nothing reaches a student unread.
When three departments set major work in the same week, you find out while there is still time to move something.
Subject channels with teacher moderation, a slow mode for the noisy ones, and no direct messages between staff and students outside a logged channel.
Take it from the class list on your phone in about ten seconds, or let it follow from the calendar and correct the exceptions.
We are not going to tell you we can detect AI writing. Nobody can, reliably, and the tools that claim to are wrong often enough to ruin a student's year. So we built the opposite thing.
Compass shows how a piece of work was built — when it was started, what was drafted, where it stalled. A conversation starter, not an accusation.
When a student uses Shiba on work linked to an assignment, the transcript is available to them and attachable by them. You ask; they show.
Per assignment: no AI, AI for planning only, or AI freely with disclosure. Students see the rule before they start, in the assignment itself.
On flagged coursework, Shiba explains and questions but will not produce the artefact. It says why, and it says who set the rule.
This shifts the question from "did a machine write this" to "can you explain what you wrote", which is a better question and one you were probably already asking.
| No training on student work | Coursework, messages and assistant conversations from a school account are never used to train models. This is not a setting a district can be talked into turning on. |
|---|---|
| No advertising, ever | There is no ad product. Nothing about a student is packaged for anyone outside the school. |
| No selling to third parties | Profile data obtained through school sign-in may not be sold, brokered or merged into an outside graph. Our processors are listed in the trust centre. |
| No surveillance features | No keystroke logging, no webcam proctoring, no location tracking, no screen monitoring. We have been asked for all four and declined each time. |
| No lock-in | Export the school's data whenever you like, in a format you can read. Leaving is a button, not a negotiation. |
A single class, about ten minutes. A whole school with verified registration and a timetable import, usually an afternoon with someone from us on a call.
No. Cadence runs in a browser on shared machines, and signing out is genuinely signing out — preferences and sessions do not linger for the next person.
Cadence is free for schools. Compass is paid per student with a free tier, and there is a reduced rate where cost is the blocker — ask rather than assuming. See pricing.
Yes. The feed, calendar, channels and attendance work with every assistant feature switched off at the school level. Some schools run it that way for a term first.
It belongs to them. They keep a personal copy under their own Noctic Account; the school's copy follows the school's retention policy.
Support, and during term we answer school reports first. Live status is on the status page.
Noctic Education
Rollout, identity, data protection and the paperwork your procurement team is going to ask for.
We are a small company. That has consequences worth knowing before you start a procurement process with us, and they are set out plainly below rather than buried in a call.
We start small on purpose. A single cohort with real timetables surfaces more problems in a week than a pilot document does in a month.
SSO wired up, verified registration switched on, timetable imported and checked by the people who wrote it. This is the part that takes the longest and the part worth not rushing.
Staff onboarding runs about an hour. Students need no training, which is not a boast — it is the test of whether the interface is right.
School by school, with the first school's staff usually doing more of the explaining than we do. Then a review of what to switch off, which is always something.
SAML 2.0 against your existing directory, so accounts are created and de-provisioned where you already manage them. Google and Microsoft directories both work.
A student account tied to a school is confirmed by the school, not self-asserted. This is what makes channels safe and what stops outsiders appearing in them.
Student, teacher, head of department, administrator, guardian. Permissions follow the role, and the role follows your directory.
Staff accounts finish every sign-in with an emailed code, and five failed passwords lock the account and email an unlock link. Not optional, not configurable downward.
Linked, read-only, scoped to their own child, and visible to the student. No silent parental monitoring — everyone can see who can see what.
Who changed a permission, who exported data, who accessed a record. Exportable, and retained for the period your policy requires.
| Controller and processor | The school or district is the controller. We are the processor and act on your instructions. A data processing agreement is available before you commit to anything. |
|---|---|
| Residency | Canadian and EU regions available. Data stays in the region you choose, including backups. Tell us the region before rollout, because moving it later means a migration. |
| Retention | You set it per data class. Deletions propagate to backups within thirty days, and we will tell you when it has completed rather than leaving you to assume. |
| Training | School data is never used to train models. There is no consent flow that changes this for a school account, deliberately, so it cannot be switched on by mistake. |
| Subprocessors | Listed publicly in the trust centre, with notice before any addition. Currently a short list, because we run most of it ourselves. |
| Incidents | Notification within 72 hours, and in practice as soon as we know. Our track record and our process are both on the status page. |
A procurement process will find these anyway. Better that you hear them from us first.
If you need a vendor with a hundred-person support organisation and a decade of district references, that is not us yet. What you get instead is direct access to the people who build it.
Current status, honestly stated, is in the trust centre. If a specific certification is a hard requirement for you, ask before starting — we will tell you straight whether we have it.
Cadence is production software used daily. Compass is in preview. Do not build a district-wide plan around Compass features on a fixed date.
Proctoring, keystroke logging, webcam monitoring and location tracking are not on a roadmap we are willing to be talked into. If those are requirements, we are the wrong supplier.
Cadence is free for schools. Compass is per student. There is a reduced rate where cost genuinely blocks access, and beyond that there is not much room to move.
Ecosystem
Ours and other people's. Every one of them asks for specific permissions, and every one can be cut off from your account in a single click.
This is the whole list, not a curated selection. An app appearing here means it has registered and passed review — it does not mean we vouch for what it does with a permission you grant it.
Shiba
Parable 4.5 at every effort tier, Agent Mode, artifacts, voice and memory.
Cadence
Feed, calendar, notes, channels, messages and verified school registration.
Compass
Reads your Cadence data, plans in short blocks, tutors the specific gap.
Momentum
A glowing streak matrix, a thirty-second evening check-in, stored on your device.
Noctic Account
Identity, plan, privacy and the consent screen every app has to pass through.
Four scopes. No bundles, nothing granted by implication, and each one refusable on its own without refusing the rest.
| identity | That you are a real signed-in person, and a stable ID for you. Nothing else — not even your name. |
|---|---|
| profile | Display name, avatar and verification badge. What other users can already see. |
| Your address, so the app can contact you. The most commonly refused scope, and rightly. | |
| api | Model requests on your behalf, counted against your plan and shown in your usage. Reviewed by a person before an app may request it. |
Your date of birth, plan history, moderation records, private notes, direct messages and assistant conversations are not available through any scope. There is no partner tier that unlocks them, and there is no price at which we will add one.
The consent screen names the app and lists exactly which scopes, before anything is granted.
Connecting the wrong account is easy to do and easy to undo — switch on the consent screen and sign in as whoever you meant.
What each app asked for and when you approved it, in your account. Nothing hidden in a submenu.
One button ends access at once. No grace period, no token that keeps working for another hour.
Every app is checked for a working redirect, an honest name and a real homepage before it can request
anything beyond identity. Apps requesting api are reviewed by a person. We do
not audit what an app does with data you have chosen to give it.
Revoke it from your account first, then tell us at support. Selling or brokering profile data obtained through sign-in breaks our terms and gets an app removed.
No. There is no scope that exposes assistant conversations, direct messages or private notes, and this is enforced at the token level rather than by policy alone.
Because we made it a separate scope so you can say no to it. An app that genuinely needs to email you will explain why; one that does not will still ask, and you can decline.
Register it, ship it, then write to us. See build on Noctic.
Ecosystem
Continue with Noctic is open to apps that are not ours. No fee, no revenue share, no approval queue for the ordinary case.
The bargain is simple. You get an identity layer you did not have to build, with sign-in codes, lockout and recovery already handled. Users get one consent screen they recognise and one place to revoke you.
Password rules, breach checking, emailed sign-in codes, account lockout and unlock links — all of it already built and maintained on our side.
The same screen across every app in the ecosystem. Familiarity is worth more than a custom flow, and it converts better than one people have never seen.
Authorisation code with PKCE. If you have integrated any other provider, you already know this. No bespoke SDK you have to adopt.
A verified badge earned in one product is recognised in yours, so you do not have to run your own identity checks.
URL builder, PKCE generator, token exchange tester, token inspector, userinfo explorer and a webhook signer. All in the developer section.
With the api scope your app can make Parable requests counted against the user's plan
rather than a bill you have to underwrite.
Name, homepage, redirect URIs. You get a client ID and a secret shown once.
Build the authorisation URL with a fresh state and PKCE challenge. Our builder will check it.
Server-side, within sixty seconds, for an access token and a refresh token.
Call userinfo, key your records on sub, and enforce the scope on every request after.
Short, and we do enforce them. Breaking any of the first three gets an app removed rather than warned.
| Do not sell the data | Profile data obtained through sign-in may not be sold, brokered, or merged into a third-party identity graph. This is the one we remove apps for most often. |
|---|---|
| Do not impersonate Noctic | Use the official button and the official name. Do not imply we built your app, endorse it, or review its content. Details in brand. |
| Ask for the least you need | Requesting every scope because it is easier is grounds for review. A narrow request is also approved by more users, so this is in your interest anyway. |
| Handle revocation properly | When a user revokes you, stop. Treat a sudden 401 as revocation and send them back through authorisation rather than retrying in a loop. |
| Keep the secret secret | Server-side only. A secret in a front-end bundle or a mobile binary is a published secret, and we will ask you to roll it. |
| No apps aimed at under-13s | A Noctic Account requires 13 or older. Do not build a flow that encourages younger users to claim otherwise. See children and teens. |
Nothing. No listing fee, no revenue share, no per-user charge for identity,
profile or email. The api scope draws on the user's plan.
Honestly, not many yet — we are a small company with a handful of products. Build on this because the integration is clean and the terms are fair, not because of the distribution.
Possibly, and we will not pretend otherwise. What we will not do is use anything we learn from your integration to do it. We do not read your traffic for product ideas.
Twelve months' notice for any breaking change to the authorisation flow, and we would publish the wind-down in the changelog and the newsroom rather than emailing you quietly.
Yes, per token and per app. Generous for sign-in traffic, real for api. Ask before
launching something with unusual volume and we will raise it.
Register a second app for development with http://localhost redirects. Keep it separate
from production so a leaked development secret cannot touch anybody real.
Trust centre
Where your data lives, who else touches it, what we have certified and what we have not.
Most trust pages are written to survive a procurement questionnaire. This one is written to be read, which means it says "not yet" where that is the truth.
| GDPR | Compliant Data processing agreement available, EU residency offered, subject access and erasure requests handled within thirty days. |
|---|---|
| PIPEDA | Compliant We are a Canadian company and this is our home regime. Canadian residency is the default for Canadian schools. |
| FERPA | Aligned School data is processed on the school's instruction as a school official. No secondary use, no advertising, no training. |
| COPPA | Not applicable by design A Noctic Account requires 13 or older. We do not knowingly collect from under-13s. See children and teens. |
| SOC 2 Type II | In progress Observation window underway. We do not have the report yet, and we will not imply otherwise. Ask for a current date if this gates a decision. |
| ISO 27001 | Not started On the list, not begun. If it is a hard requirement, we are not the right supplier this year. |
If a certification matters to your process, write to us and we will give you the current position in writing rather than a marketing answer.
Canada (default) and the European Union. The region covers primary storage, replicas and backups. It is chosen at setup, and changing it later is a migration rather than a switch.
TLS 1.3 in transit, AES-256 at rest, and separate keys per region. Database backups are encrypted with keys we hold rather than the storage provider.
Continuous, with point-in-time recovery over 30 days. A deletion propagates through backups within the same 30 days, and we confirm when it has.
Production access is limited to named engineers, requires two-factor, and is logged. Nobody has standing access to message contents or assistant conversations.
The complete list. We are told regularly that it is unusually short — that is because we run most of the stack ourselves rather than assembling it from ten vendors.
| Supabase | Database, authentication and object storage. Region-pinned. Processes account and application data. |
|---|---|
| Netlify | Static site delivery for noctic.ink. Serves pages and assets; holds no account data. |
| Cloudflare | DNS and denial-of-service protection. Sees request metadata in transit, not content at rest. |
| Transactional email provider | Delivers sign-in codes, unlock links and account notices. Receives an email address and the message body, nothing further. |
We give thirty days' notice in the changelog before adding a subprocessor that touches school or account data. Districts on a data processing agreement are notified directly.
Stop the bleeding first — revoke, isolate, roll credentials. Before any communication goes out.
The status page is updated while we still do not know the cause. Silence during an incident is worse than an incomplete update.
Affected schools and users within 72 hours of confirming a data incident, and in practice as soon as we can describe it accurately.
A post-mortem with the actual cause, published. No "an issue with a third party" when it was our mistake.
Tell us before you tell anyone else and we will work with you. We do not threaten researchers, and we do not require you to sign anything before reporting.
Through contact with "security" as the topic. We acknowledge within one working day and give you a real assessment within five.
noctic.ink, shibaai.dev, the Cadence application, our authorisation endpoints and our edge functions. Third-party marketing pages and our subprocessors' own infrastructure are not.
Do not access accounts that are not yours, do not run denial-of-service tests, and do not exfiltrate data to demonstrate a finding. A description is enough.
Not a formal programme yet. We pay for serious findings out of proportion to our size, and we credit you publicly if you want that.
Yes, once it is fixed, with your credit if you want it. Ninety days is our default ceiling and we usually beat it considerably.
Changelog
Every user-visible change, including the ones that were our fault. Breaking changes are marked and given notice.
The newsroom is for announcements. This is the running record — smaller, duller and more useful if you are trying to work out when something moved.
The family is now four machines. Aeon™ and Aeon™ Neo are new desktop-class computers, one full-size and one small enough to carry. The laptops are called Aebook™, and the lineup keeps two of them: the Aebook™ Nano and the Aebook™ Pro. The 13.4-inch and 14.2-inch laptops are gone. The family page, the builder and the questionnaire were rebuilt around it.
Aeon™ Nano, Aeon™ Neo, Aeon™ Ultra and Aeon™ Pro each have their own page now, with the full specification, the ceilings and the reasons to buy something else. The Nano is new: an Intel N100, 8 GB of memory and either 64 GB or 500 GB of storage, fanless, and the cheapest machine we could design without it being a bad one. The lineup page keeps the comparison.
Registration and sign-in now both finish with a six-digit code sent to your address. Five failed passwords lock the account and email an unlock link. Not optional — a password alone no longer signs anyone in.
Connecting an app while signed into the wrong account used to mean signing out and starting over. The consent screen now shows which account you are connecting and lets you switch in place.
Notification preferences, appearance controls including accent colour and text size, account privacy, session management and a data export. Preferences save as you set them.
Every text and background pairing across the site was measured and fixed. Cards that were hard-coded dark now follow your theme, and code blocks finally switch palette in dark mode — they had been stuck on the light one because of a selector that never matched.
A new page for the x86-64 processor family we want to build: the microarchitecture, the manufacturing process end to end, the patent situation in plain language, a five-rung plan from software simulator to laptop part with a cost against each rung, and the ways it could all fall over.
The lineup is respecified around Core Ultra 5 226V, Core Ultra 7 258V and Core Ultra 9 285H — real parts with on-package memory — so the machine and AXESS OS can be judged now. Every badge reading “work in progress” now reads “concept”, which is what it always meant.
A second chip in the Aeon™ concept: 4 cores, 4 threads, up to 3.4 GHz, fanless, alongside the 8-core A1 at up to 3.8 GHz. Same architecture, so one build runs on both. Both are now Noctic Silicon targets rather than Aeon™ specifications.
The URL builder, PKCE generator, token exchange tester, token inspector, userinfo explorer and webhook signer all gained explanations of what the parameters mean and what the errors are telling you.
Six effort tiers, a one-million-token context window that holds instructions to the end, and better calibrated uncertainty. Published limitations alongside it.
Third-party apps can register and use the authorisation flow. Four scopes, no fee, no revenue share.
Verified school registration, timetable import from a photograph, channels with teacher moderation. Free for schools.
Twelve months for the authorisation flow, ninety days for anything else in the API. Announced here first, then by email to registered developers.
Parable 4.5 stays 4.5. We do not quietly swap the weights behind a version number, because that makes your evaluations meaningless.
Anything on the way out gets a date, not a "soon". If we miss the date, the date moves publicly rather than the removal happening early.
Outages and their post-mortems are on status. This page is for intentional changes.
Concept hardware · 100 reservations
Put your name on the list. No payment now, and no payment at release until you say yes.
One hundred spots, held in the order requests arrive. We confirm your place by email — we would rather tell you honestly where you are in the queue than show you a number on a page that we cannot back up.
Name, email, and which of the four models interests you. That is the whole form.
Within a few days, with your position. If the hundred are gone you go on the list behind them.
Only when something real happens — a manufacturing partner, a date, a price. Not a newsletter.
We ask you to confirm before anything is charged. Say nothing and nothing happens; your spot simply passes to the next person.
We ask for as little as we can get away with. No address, no card, no date of birth.
Reservations are held against an account so that only you can change or cancel yours, and so we are not keeping a second list of names and addresses we do not need. It is free, it takes a minute, and it does not commit you to buying anything.
Sign in or create an accountAlready signing in on another tab? This page will notice and swap itself over. What a Noctic Account is.
We have you down for an Aeon™ and will confirm your position to your address. Nothing has been charged, and nothing will be without you confirming first.
No. It is a list, not a contract. You can leave it with one email and there is no penalty, no deposit and nothing to forfeit.
Not now and not at release until you confirm. We do not hold a card, and this page never asks for one — if a page claiming to be us ever does, it is not us.
You go on the list behind them, in order, and we tell you that plainly in the confirmation email rather than pretending you made the first run.
We do not know. There is no manufacturing partner, no date and no price. Anyone giving you a quarter for this machine is guessing. See where the concept stands.
Yes, right up to the point you confirm an order. Reply to the confirmation email and we will change it.
They sit on the reservation list and nowhere else. Not sold, not brokered, not used to train anything. The full terms are in the Privacy Policy.
So the reservation belongs to someone. It means only you can change or cancel yours, you can see it from your account, and we are not maintaining a separate list of names and addresses outside the thing that already holds them.
No on both. It is free, it is the same account that works across every Noctic product, and marketing email is off unless you turn it on in Settings.
Company
One person, for now.
Most companies our size publish a page like this with five titles and four photographs of the same three people. Here is the honest version instead.
Founder and Chief Executive Officer · Chief Hardware Engineer · Chief Software Engineer
Not three people. One person holding three titles until there is someone better to hand each of them to.
| Chief Executive | Decides what we build and what we refuse to build. Answers the email. Says no to the surveillance features schools keep asking for, and will keep saying no. |
|---|---|
| Chief Hardware Engineer | The Aeon™ and Aebook™ concepts — the four machines, the decision to ship on Intel Core Ultra until our own silicon exists, the Aether chip targets behind Noctic Silicon, going USB-C only and putting memory in the package where it cannot be upgraded. |
| Chief Software Engineer | AXESS OS and the Glass UI, Cadence, Compass, the Noctic Account, the sign-in codes, and every line of the site you are reading. |
| Everything else | Support tickets, the privacy policy, the status page during an incident, and the invoices. There is nobody to escalate to, which is either reassuring or alarming depending on your role. |
I started Noctic because the software I was given at school was bad in ways that seemed fixable, and because the tools that were supposed to help mostly watched you instead. Cadence began as one school's problem. Everything after it came from the same place.
I hold three titles because there are not three people yet, not because I am uniquely qualified for all of them. I am better at software than at hardware, and better at both than at running a company. Where that shows, it shows — and I would rather you heard it here than found it out later.
The plan is to hand each of these titles to someone who does the job properly, and to keep the parts I am actually good at. Until then, if you write to Noctic, you are writing to me. and something about Baja blast i guess...
Nicholas Steiche
Founder, Noctic
Worth weighing honestly, whichever side of it you are on. Some of this is in your favour and some of it is not.
No tier-one script, no account manager relaying your question to engineering. The reply comes from whoever can actually change the thing.
"No advertising, no training on school work, no proctoring" holds because there is no board, no investor and no growth target pulling the other way.
The real risk, stated plainly. It is why your data is exportable at any time and why nothing we build locks you in — leaving has to work even if we stop.
Certifications, compliance paperwork and enterprise procurement all take longer here than they would at a company with a legal team. See the trust centre for exactly where things stand.
During term, school reports get answered first. Everything else is answered too, just not always the same day.
Small enough that shutting something down would be a conversation, not a line in a changelog you find three months later.
These are the titles above, written as the jobs they will become. None are open on a fixed date, and we will not pretend otherwise — but this is the order we would fill them in.
The product with real users and real schools depending on it. The first hire, whenever it happens.
Someone whose actual job is answering schools, rather than it being the fourth thing on a list.
Aeon™ needs a person who has shipped physical products before. Currently it has someone who has not.
Compliance, contracts, invoices and the certifications sitting in the trust centre marked "in progress".
If you are reading this because you are considering working here: the honest pitch is that you would be the second person, and you would have a great deal of say in what Noctic becomes.
That did not work, and it is our side of the line rather than yours.
Nothing you were doing has been lost, and nothing on your account has been changed. Most of the time the same thing works on a second attempt.
A single failed request is the most common cause, and a retry clears it.
If something of ours is down it will be on status already, usually before we know the cause.
A long-open tab can be holding an old version of the site after we have shipped a new one.
If it keeps happening, send us what it says above through contact. That text is the useful part.
No. Forms on this site hold what you typed until they succeed, and nothing is written to your account unless the request came back clean.
No. Nothing on Noctic charges you without an explicit confirmation step, and a failure like this stops before that point.
Yes. Sign-in needs your password and a code from your email, and a page error cannot change either. If you want reassurance, end every session from Settings.
That is worth telling us about, with the page address and the text above. Write to support and we will chase it rather than wait for a pattern.
Noctic Developer
The model, the account and the design language, in one membership.
Everything Noctic runs on is open to you: Parable for reasoning, the Noctic Account for sign-in, Cadence for classrooms, Glass for the way it all looks. The Developer Program is how you get the parts of it that carry our name — a publisher name on record, published listings, hardware and the people who built it.
What's new
Six effort tiers behind one endpoint, with the reasoning trace returned rather than hidden. Streaming, tool calls and structured output are all in the same shape as the chat surface you already know.
Read about ParableThe material Noctic is drawn in — surfaces, depth, the motion curves — written down properly, with tokens you can lift straight into your own product without guessing at the numbers.
Open Just GlassMembers can request a unit from the Aeon™ line to test against real silicon rather than an emulator, and keep it for the length of the membership year.
See the Aeon™ lineMembership
You can build against Noctic without joining — the OAuth endpoints, the tools and the examples are open to any account. The Program is for the things that need a name attached: a named publisher on the consent screen, a listing in the Ecosystem, early builds, hardware, and a person to talk to.
Events
Sessions, labs and meetups, online and in the room. Members get the labs — an hour with an engineer and your own code on the screen — before anyone else.
Standard OAuth 2.0, three steps, with six tools for inspecting every part of the flow.
Open the documentationPush what a class website publishes into Cadence, under the class it belongs to.
Read the docsThe Noctic look as a skill for Claude and a stylesheet for you, with the rules for our marks.
Get the design kitA Next.js 15 app with auth, billing and workspaces already built. $199, source included.
See what is in the zipNoctic Developer Program
One year. Renewed when you say so.
Enrolment verifies who you are, asks what you intend to build, and puts a name we can stand behind on every consent screen your app shows. It takes about ten minutes. Nothing in it is a test.
The legal name you enrolled under, shown on the consent screen above the scopes your app asks for, and held to an agreement that ends if it is false. Apps outside the Program say "an unverified developer" there instead, and people notice.
Apps that sign in with Noctic can be listed at Ecosystem → Apps, where people who already have an account go looking for things to connect it to.
Ten times the unauthenticated rate limit on the token and userinfo endpoints, and a queue position on Parable that does not move behind free traffic.
Models, endpoints and Glass revisions before they ship, with the breaking changes written down in advance rather than discovered.
Not a ticket queue — an engineer reads your code and answers about your code. Organisation membership gets six.
Request an Aeon™ unit for the membership year. When developer labs start running, members get the seats before anyone else — there are none scheduled yet.
All four are free. There is no fee to enrol, no fee to stay, and no card to put on file — what you choose here decides whose name goes on the consent screen and what the membership is allowed to do, not what it costs.
| Individual | One person, publishing under their own name. Two support requests, one Aeon™ unit, everything above. The name on the consent screen is your legal name. |
|---|---|
| Organisation | A company, publishing under the company's name. Up to twenty-five people on one membership and six support requests. The name on the consent screen is the organisation's. |
| Education | A school, college or university. Everything in Organisation except hardware, and no entity number is asked for — plenty of institutions do not have the kind we mean. |
| Enterprise, in-house only | Apps distributed inside your own organisation and never listed publicly. Includes private scopes and a named contact. |
Pick the one that describes you rather than the one that sounds biggest. It sets what your membership may do, and changing it later means enrolling again.
Everything is done as you, so we know who agreed to what. Free, and it takes a minute.
Eight questions about what you are building, who it is for and what happens to their data. There are no right answers.
Legal name, or the entity and your authority to sign for it. This is the name you are held to.
An automatic check sends back anything missing or contradictory on the spot. A complete application goes to the Noctic Developer team, who accept or decline it.
Automatic, and immediate. It reads what you have given for the things that contradict each other or are not there, and answers on the spot.
Live the moment it is accepted. Free, with nothing to pay now or later.
If your enrolment is declined we say which of these it failed and what would change the answer. It is not a permanent bar unless it says it is.
Step 4 of enrolling
There are no right answers. Nothing here is marked.
A membership is an agreement about a specific thing you intend to do, so the review reads better when we know what that thing is. Answers route the application — a product for under-sixteens is checked against a different set of rules than an internal dashboard — and they are not a test you can fail. Say "not sure yet" wherever that is the honest answer; it is one of the options for a reason.
Your answers are saved against your Noctic Account, alongside the rest of the enrolment.
An internal dashboard and a product for schoolchildren are read against different rules. Telling us which one you are building is how the right person picks it up.
Some answers come with a pointer — to the rules on minors, or on passing profile data to a third party. That is a note, not a mark against you.
Plans move. Come back and edit any answer while the enrolment is still a draft, and tell us in writing once it is a membership.
The one thing that is not flexible: the answers have to be true when you give them. A membership rests on them, and an answer that turns out to be false ends it.
Noctic Developer Program
Five steps, free, and read by the Developer team.Five steps, free, answered on the spot.
Your answers are saved as you go, so you can leave in the middle of this and come back to it. Nothing is submitted until the last step, and there is nothing to pay at any point — membership is free. Anything missing is caught the moment you submit, so the only wait is for the team to read a complete application.The check at the end is automatic, so you get the answer immediately rather than in a few days.
Enrolment is an agreement between Noctic and a named person, so it happens as you rather than as an anonymous form.
This decides whose name goes on the consent screen, and it cannot be changed afterwards without enrolling again.
As they appear on the identity document you would show a bank. Initials and nicknames fail review.
Where the review decision goes. Defaults to the address on your Noctic Account.
Exactly as registered, including the suffix. This is the name people will see.
Nine digits, issued once against a registered company. The check is automatic and nobody looks these up for you, so it has to be here — it is in your own incorporation documents.
Checking your answers…
This is what gets checked. Nothing here costs anything — membership is free.
Two readings. A machine first, the moment you press the button, so nobody waits on a person to be told a box is empty. Then the Noctic Developer team, who read what is complete and decide.
Nobody reads it. The check runs the moment you press the button and answers in the same breath, so there is no queue to be at the back of and no working day to wait for.
Against itself, mostly: fields that are missing, an organisation enrolling from a personal mailbox, a name that is only initials, a declaration left unticked. Anything it finds comes straight back with the list of what to change — fix it and submit again, as often as you need.
A complete application waits with the Developer team, who accept it or decline it with a note written for you. Spot a mistake while it waits? Withdraw it, change it, send it again.
A complete application is accepted there and then. Sent back is not a refusal — fix what it named and submit the same form again.
Membership is live and free from the moment it is accepted. There is nothing to pay and no card to add.
Worth being straight about what an automatic check is: it reads what you typed. It does not confirm that a company exists, that you work there, or that a legal name is the one on your passport. What it does is hold you to the declarations you ticked — and those are the thing the membership rests on. An answer that turns out to be false ends it, whoever or whatever accepted it.
Noctic Developer
The first one is an hour with our CEO, online, on 20 October.
Sign up with the Noctic Account you already have and the link to join appears on this page. It goes ahead if at least one person signs up: sign-ups close an hour before it starts, and if nobody has by then it does not happen, so nobody is left sitting in an empty room.
What is scheduled is above. These are the shapes the rest take when they are — said here so you know what to expect, not as promises with dates on them.
An hour on one thing, streamed and kept up afterwards. Open to anyone with a Noctic Account.
Your code on the screen and an engineer beside it, no slides. Small enough that they would fill, so members of the Program would get them first.
Run by people who are not us, in their own city. We would send stickers and a speaker where we can.
Anything scheduled goes in the changelog as well as on this page.
Somebody has to be first, and it does not have to be us. If you would organise a Noctic developer meetup in your city, say so — we will help with stickers, a speaker where we can, and the slides for anything we have shown publicly. Use the mark the way the brand guidelines describe and call it a Noctic Developer Meetup, not a Noctic event.
Noctic Developer
Where you are, and what is next.
Keys of both kinds live on the main site with the rest of your account, because they belong to the account rather than to the membership.
Noctic Developer
Straight from the team that builds Noctic.
Releases, heads-ups, events and anything else worth a developer's attention, posted by the Noctic Developer team as it happens. Pinned shouts stay at the top until they stop being true.
The latest three sit at the top of developer.noctic.ink, above everything else that is new.
Open DiscoverAnything that changes how an API behaves is written into the docs as well as shouted about.
Read the documentationReleases are recorded in the changelog for good, long after the shout has scrolled away.
Open the changelogNoctic Developer · Team
Everyone enrolling in the Program, and your decision on each.
Loading…
One key per buyer. It downloads the Kick Start zip once — the buyer enters it on Kick Start. If a download fails, reopen the key and it works again.
New key for
Who has signed up, and the link they join on. Paste the Meet link here and everyone who signed up sees it on the events page — nobody else does. An event nobody has signed up for by the time sign-ups close does not happen, and the page says so without anybody having to do anything.
Error 404
The page has either moved or never existed. The rest of the site is still here.