JPTalk with the founder

Early-stage product development · Japan

Rights operations software for the age of generative media.

Panezy is building a workflow system for game, anime, character, and VTuber rights holders—designed to turn each IP's policies into consistent case review, human approval, and decision records.

Not all fan-created content is a problem. The goal is to make responsible creation easier to navigate while rights holders retain control over permission, enforcement, and brand decisions.

Open interactive prototype Discuss an early pilot

Product development is at an early stage. Customer needs, willingness to pay, and the final product scope are still being validated.

Illustrative workflow · not a live customer workspace
CASE#UGC-012

AI-generated short video

Commercial signalPresent

AttributionMissing

Official confusionReview

RECOMMENDED ROUTEHuman review

Request brand and rights review

  • Attribution condition is not met
  • Commercial intent needs confirmation
  • Final authority remains with the rights holder

Policy in.

Reviewable recommendation.

Human decision.

Auditable history.

32-second product walkthrough

See the prototype workflow in motion.

A fictional content case moves from an IP policy to a reviewable recommendation, a rights-holder decision, and a shared audit history.

Try the interactive version
Product prototypeFictional IPSample dataNo external systems connected

Planned workflow

From a written policy to a reviewable decision.

The planned system connects rights-holder-defined rules with the context of each content case. It prepares the information; people retain the authority.

  1. 01

    Structure the policy

    Turn rights-holder rules, approved examples, and exceptions into reviewable conditions.

  2. 02

    Organize each case

    Capture the content type, context, commercial signals, attribution, and missing information.

  3. 03

    Recommend a route

    Compare the case with the applicable policy and prepare a recommendation with its rationale.

  4. 04

    Keep the decision trail

    Connect human approval, evidence, communication, and the eventual outcome in one record.

Human control is part of the product design. AI may assist with classification and policy matching, but it will not make final legal determinations. Rights holders—or their appointed professionals—retain final authority.

Product scope

The software we are building.

One structured workspace for policies, content cases, reviewer decisions, and the evidence behind them.

Policy workspace

Structure rules by platform, content type, AI use, commercial use, attribution, territory, and exception.

Data model in development

Case triage

Bring cases into a shared queue and surface policy fit, review priority, and missing information.

Planned software module

Human approval

Route unclear or sensitive cases to the right licensing, brand, rights, or legal reviewer.

Planned software module

Evidence and history

Keep the applicable rule, evidence, recommendation, approval, communication, and outcome connected.

Planned software module

Initial delivery model

Software-led, with human operations at the start.

The initial pilot model is designed to combine a narrow software workflow with managed onboarding and operations while real requirements are still being validated.

A pilot would focus on one IP, one platform, and one type of user-generated content. Panezy would help structure the policy, organize cases, and prepare recommended next steps. The rights holder would approve rules, exceptions, permissions, and any external action.

The operations are a way to learn what should become repeatable software—not the final shape of the company.

Development status

Clear about what exists—and what comes next.

Live today

Company and public infrastructure

  • Panezy was established as a company in Japan in June 2026.
  • This public product site is deployed on Cloudflare Pages.
  • A public interactive prototype demonstrates the intended workflow with fictional IP and sample data.
In development

Product definition

  • Requirements and workflow specification
  • Data models for policies, cases, evidence, decisions, and actions
  • Initial pilot design and customer problem discovery in Japan
Planned

First product version

  • Web application for policy management, triage, and human approval
  • Production API and structured case database
  • Authorized, platform-specific data connections

Panezy does not yet claim a production software deployment, customer implementation, platform partnership, proprietary dataset, or automated licensing and payment capability.

Cloudflare architecture

A focused stack for policy, cases, and evidence.

Only the public site is live today. The application architecture below is planned for the first product version.

LIVE

Cloudflare Pages

Hosts this public product site.

PLANNED

Cloudflare Workers

APIs, workflow logic, and policy-evaluation services.

PLANNED

Cloudflare D1

Structured records for policies, cases, decisions, and actions.

PLANNED

Cloudflare R2

Permissioned evidence files and reports with appropriate retention controls.

Long-term direction

Move beyond takedowns toward authorized participation.

Panezy's long-term goal is not to create another social network or prohibit fan creation by default. Where a rights holder chooses to permit a use, the system could guide creators toward attribution changes, individual approval, or agreed licensing conditions.

Future payment or revenue-sharing workflows would depend on rights-holder approval, customer demand, legal validation, and agreement between the parties.

Help shape the product

How does your team handle real cases today?

If you work in IP rights, licensing, brand management, or fan-content policy, we would value a conversation. We are looking for interview partners and potential early-pilot collaborators—not presenting a finished product.

Talk with the founder