AI side businesses · University student founders · Creator products

Turn what you are learning or building with AI into a product people can run.

Build a Living Surface for study, work, or an AI-powered side business. Keep it useful with local routines, then publish the reusable product when it is ready.

University student foundersAI side businessesCreator products
See the product workBuild and publish

Local creation and free publishing do not require a membership.

Own the files

Your vault is a plain folder. Open it, copy it, move it, or back it up.

Bring the agent

Connect Claude Code, Codex, or another local runtime. Lorevik is the surface, not the model.

Share the Surface

Prepare the reusable method and interface as a review-ready package, separate from the owner's working vault.

Inside the app

Watch useful local work become a reusable product.

One persistent Lorevik window carries two real Living Surface captures through a Local Agent run, an illustrative Routine concept, a composed Morning Brief, and a review-ready marketplace package.

01 · Calendar - A scoped Local Agent fills a real Calendar Surface inside the workspace.

Lorevik · Calendar

02 · AI Usage - Concept preview: a proposed 07:00 workflow would write local usage into a daily Surface.

Lorevik · AI Usage

03 · Morning Brief - Calendar and AI Usage pull out and dock into one board.

Lorevik · Morning Brief

04 · Explore - The same review-ready package can move toward marketplace distribution.

Lorevik · Explore
Concept preview · not current runtime

Concept preview: at 07:00, only the routines that are due move.

This storyboard explores future mixed-source writes and cadences. Current Routines do not provide the calendar-to-AI-usage write, every-second-day timing, or Sunday-specific weekly timing shown below.

07:00

Daily

Every morning

01 · due routine

Close yesterday, then open the day

This future workflow would close the previous local usage window, combine approved calendar context, and write a day opening without another model call. That mixed-source write is not in the current runtime.

01 · Source

Local usage + calendar

Configured local files

02 · Run

Local bridge

Deterministic close and summary

03 · Write

ai-usage/data.json

Feeds Morning Brief

Day opening

ai-usage/data.json

Written locally
Close

Yesterday · usage window closed

Read

Today · commitments gathered

Open

Morning · first focus surfaced

07:00

Every 2 days

Every second day

02 · due routine

Turn new research into something teachable

This future workflow would turn approved notes into a sourced brief and practice loop. Every-second-day timing at 07:00 is illustrative, not a current schedule type.

01 · Source

Approved research notes

Source links stay attached

02 · Run

Local agent

Source-bound synthesis

03 · Write

learning-brief/data.json

Feeds Morning Brief

Learning brief

learning-brief/data.json

Written locally
Idea

Explain · one sourced concept

Try

Practice · one small exercise

Recall

Review · next question queued

07:00

Weekly

Every Sunday

03 · due routine

Review the creator loop

This future workflow would group local publishing, audience, and support signals into one next move. Sunday-specific weekly timing is not a current schedule type.

01 · Source

Creator workspace

Publishing + support signals

02 · Run

Bridge + local agent

Groups signals, then drafts

03 · Write

creator-pulse/data.json

Feeds Morning Brief

Creator pulse

creator-pulse/data.json

Written locally
Ship

Publish · queue reviewed

Hear

Listen · questions grouped

Choose

Decide · one next move framed

04 · Composed output

Morning Brief

The day opening, learning brief, and creator pulse meet in one Surface while their source files and schedules stay distinct.

Architecture

Private work runs locally. Discovery and commerce run on the web.

Lorevik separates the runtime from the marketplace. Your vault, raw inputs, owner Data JSON, agent sessions, and routines stay on your machine by default. The web handles accounts, listings, submitted listing metadata, transactions, and explicit package delivery.

Desktop runtime

Private work happens here

Local by default
01

Local vault

Plain files you can inspect, move, and back up.

02

Local bridge

Connects the visible Surface to the desktop runtime.

03

Your agent

Claude Code, Codex, or another compatible local runtime.

04

Living Surface

An interface filled with owner data on the owner's machine.

Routine closes the local loop

Refresh a Surface or reopen a saved board without turning the owner's workspace into a cloud job.

Explicit submit

Creator chooses the distribution package

Web control plane

Discovery, identity, and commerce

01

Accounts

Identity and creator profiles

02

Listings

Public descriptions and submitted listing metadata

03

Consent and audit

Records and hashes, not raw owner files

04

Commerce

Launch-gated transactions and bundle delivery

For the live workspace, cloud services receive submitted listing metadata, not raw owner vault contents. Marketplace publication is a separate, explicit path for a creator-submitted distribution bundle.

Buyer installs into a different local vault

Implemented

Local vault, bridge, Living Surface runtime, and routines

Launch-gated

Paid marketplace delivery and real-money direct charges

Not final

The full capability matrix and purchaser licence schedule

The website cannot silently reach into your vault or run your local agent.

Explore the full architecture

How it works

From a folder to a system that runs itself.

01

Keep a vault

A local folder holds your data, your surfaces, and the context your agent needs. It's plain files — visible in Finder, yours to move or back up.

02

Install a Living Surface

Browse the marketplace and download one into your vault. The smallest surface is a single instruction file; the rest can be generated on demand.

03

Your agent fills it in

The AI agent you already run reads the surface and writes your real data into it through a local bridge. No placeholder numbers — if there's nothing yet, the surface says so.

04

Add a routine

Schedule or trigger the surface to refresh itself. That's the step that turns a dashboard into something that keeps working while you don't.

Illustrative student-founder flow

Build one useful Surface. Grow it into a creator business.

Follow the same clearly labelled student-founder example from a useful local workflow to a creator-owned package, marketplace distribution, direct sale, and a recurring operating channel. The product stays the same while the business layers grow around it.

SC

Semester Command

Illustrative Learning Surface

Same Surface · one continuous path01 / 05
SC

Semester Command

Local-first Living Surface

Calendar

AI review

Brief

1

Useful local loop

Timetable + AI review + weekly brief

01 · Illustrative student project

A student founder turns one useful study loop into a product.

Implemented

Semester Command begins as a local workflow: Calendar keeps the timetable, an AI review explains model usage, and a weekly brief turns both into the next study block.

Course inputs

Living Surface

Study block

The example is illustrative, not a live listing
The product remains one local-first Living Surface
SC

Semester Command

Illustrative Learning Surface

Same Surface · one continuous path02 / 05
SC

Semester Command

Local-first Living Surface

Packaged

Calendar

AI review

Brief

2

Creator-owned package

Metadata, package boundary, review route

02 · Creator control

The same Surface moves into a creator-owned management view.

Implemented

Creator Studio shows package metadata, listing state, and review readiness. Publishing begins here, while the private working vault stays outside the listing package.

Listing readiness

Creator Studio
1

Package boundary

2

Listing metadata

3

Review route

Creator-owned management view
Workspace data is not the marketplace package
SC

Semester Command

Illustrative Learning Surface

Same Surface · one continuous path03 / 05
SC

Semester Command

Local-first Living Surface

Packaged

Calendar

AI review

Brief

3

Marketplace choice

Free listing or maintained paid listing

03 · Free or paid

One product can choose a free path or a maintained paid path.

Built · gate closed

Free publishing remains open without Creator Membership. A paid listing uses the Creator plan and the marketplace review path before checkout can open.

Free listing

No membership gate

Publish the reusable package without charging a buyer.

Paid listing

Creator plan

Submit a maintained product through the paid review path.

Free publishing is not membership-gated
Paid publishing requires Creator Membership
SC

Semester Command

Illustrative Learning Surface

Same Surface · one continuous path04 / 05
SC

Semester Command

Local-first Living Surface

Packaged

Calendar

AI review

Brief

4

Direct-charge sale

Buyer → creator as seller → platform fee

04 · Creator economy

The buyer pays the creator through a direct charge.

Built · gate closed

The creator is the contractual seller and Merchant of Record. Lorevik receives the applicable platform fee while the creator owns the customer obligation for the product sale.

Direct-charge transaction

B

Buyer

Pays creator

C

Creator

Seller and MoR

Application fee branch

Lorevik · platform service

Default platform fee policy: 10%
Founder promotional rate may apply
SC

Semester Command

Illustrative Learning Surface

Same Surface · one continuous path05 / 05
SC

Semester Command

Local-first Living Surface

Packaged

Calendar

AI review

Brief

5

Operating channel

Routine, support, refunds, opt-in signals

05 · Creator channel

A useful listing grows into an operating channel.

Planned

Sales, refund conversations, installs, opt-in usage, and paid content belong in one creator operating view. That unified layer is deliberately shown as Planned until it is connected end to end.

Creator operations

Planned product layer

Planned

Creator channel

Planned

Sales and refunds

Planned

Opt-in installs

Planned

Opt-in usage

Planned
Sales and refund operating view: Planned
Install and usage analytics: Planned, buyer opt-in required

The marketplace

Understand the surface before you install it.

Working Lorevik captures sit beside one bundled learning sample and clearly marked concept directions. Every card separates product state, publisher identity, and public activity. Metrics appear only when real marketplace data exists.

Working capture
Lorevik first-party
Lorevik sample
Bundled reference
Concept preview
Illustrative creator
Working capture

Semester Calendar

Calendar

A working timetable surface with rooms, overlaps, and alternating weeks handled in one view.

Lorevik

First-party working surface

Public activity

No public metrics

Working capture

AI Usage

AI operations

A working local view of Claude Code and Codex token usage with an explicit API-cost estimate.

Lorevik

First-party working surface

Public activity

No public metrics

Sample lesson

Agentic engineering

1Explain
2Practice
3Review

Evidence trail

Sample
Source notes
Lab attempt
Review prompt
Lorevik sampleNo memory write-back

Learning Surface

Learning

A bundled agentic-engineering sample turns source material into explanation, deliberate practice, review, and visible mastery evidence.

Lorevik sample

Bundled working sample

Public activity

No public metrics

Human-supervised run
Sample workflow
01

Research

Ready

02

Build

In review

03

Approve

Human gate

Concept preview

Productor Console

Agent console

A human-supervised agent console that carries a brief through research, build, review, and approval.

Illustrative creator

Concept identity, not a live seller

Public activity

No public metrics

Paper map

Claim
Evidence
Figure
Discussion
Source-linked note
Concept preview

Interactive Research

Research

Connect claims, sources, figures, and discussion into a paper that can be inspected instead of only read.

Illustrative creator

Concept identity, not a live seller

Public activity

No public metrics

Public noteFree
Studio logSubscriber
Living SurfacePaid release

Channel

Sample shelf

No invented sales or audience metrics.

Concept preview

Creator Channel

Creator

Organize free releases, subscriber material, and paid Living Surfaces without pretending sample activity is real.

Illustrative creator

Concept identity, not a live seller

Public activity

No public metrics

This gallery shows the range of the format. Published marketplace listings install locally and run against the owner's own data.

Browse published listings

What can become a Living Surface

One format, far more than dashboards.

A Living Surface can explain, teach, operate, track, or express. The common boundary is simple: it is an installable interface with a clear purpose, honest data paths, and an owner who decides what it can access.

Personal systems

Keep changing parts of life visible.

Calendars, assets, travel plans, health logs, reading rooms, and daily briefs can live as interfaces over files you control.

Example forms

CalendarAsset trackerMorning brief

Updated by you or a local routine

For creators

Publish what you know. Keep maintaining it.

A Living Surface is a new kind of digital asset: your workflow, your knowledge, and your judgment, packaged into something other people can install and run on their own data.

Creators publish surfaces and keep them alive by fixing, improving, and versioning the package. That maintenance is the point: a surface people trust is one someone stands behind.

Apply as a creator

Versioned package

Submit an exact package instead of exposing the rest of your vault.

Private paid delivery

Paid bundles stay behind purchase-bound access checks.

You are the seller

Creator sales route through your connected Stripe account.

Free listings stay free

A Creator membership is only required for paid listings.

Creator membership is A$29/month or A$290/year. Real-money checkout stays closed until launch review and go-live gates are complete.

Pricing

Free locally. Clear pricing for paid publishing.

Local creation and free publishing do not require a membership. Listing a paid Living Surface requires the Creator plan, whose committed price comes from the same source used by checkout.

Explore & install

Free to start

Browse the marketplace, install free surfaces, and run them with your own agent on your own machine.

Get started

Creator membership

A$29 / month

List and maintain paid Living Surfaces as a creator. The annual option is A$290; real-money checkout remains behind the launch gates.

View Creator pricing

These are committed plan prices, not a live-checkout signal. Checkout opens only after the required launch review.

Where we are

We're early, and honest about it.

We're not going to show you a wall of logos or invented testimonials. The current product already has a local vault, an agent-facing workspace, installable Living Surfaces, and a marketplace path. Publishing and real-money checkout remain behind explicit launch gates until their review requirements are complete.

No vanity metrics here. Product state is stated directly.

Be one of the first creators

Questions

The honest answers.

  • Does my data go to the cloud?
    Your raw vault files stay on your machine by default. Features that use a connector, marketplace service, or another network provider may send the data required for that feature only after you enable the relevant permission. The exact Living Surface capability and purchaser licence schedules are still under review.
  • Do I need my own AI agent?
    Yes. Lorevik connects to the agent you already run — Claude Code, Codex, or another runtime. We deliberately don't ship our own model; we're the surface and the market on top of the agent you choose.
  • Is Lorevik an app or a website?
    Both, with a clear split. The part that touches your private data runs locally on your machine. This website is where you discover surfaces, manage your account, and handle the transaction layer. Publishing starts inside the desktop Creator Studio. The website can't reach your machine or your agent on its own.
  • What exactly is a Living Surface?
    A runnable interface — a dashboard, tool, document, or view — packaged so you can install it into your vault and your agent can keep it filled with your real data. The minimum is a single instruction file; everything else can be generated.
  • What does it cost?
    Exploring, installing, and publishing free surfaces is free — always. Listing a paid surface needs a Lorevik Creator subscription (A$29/mo or A$290/yr, see /pricing).
  • Can I sell what I make?
    Paid listing prices and the Creator membership are defined, while real-money checkout stays behind Lorevik's launch review gates. When enabled, creators sell through their own Stripe Connect account and Lorevik applies the disclosed platform fee.
  • What can’t I publish?
    Anything illegal or harmful — cheating and ghostwriting, scams and account theft, pirated coursework, adult content, and the like. Sensitive areas such as health, finance, and children's education need verification and carry stricter review.

Keep your data. Run your Surfaces. Build what comes next.

Install your first Living Surface, or publish one of your own.

Get startedExplore the marketplace

Not ready yet? Join the waitlist instead.