What will you make?

A little more you.
A lot more possible.

Your apps Your data Your work

Make it yours.

Your company. Your way of working.

Build the apps you need.
Bring your apps and data together, in a space that’s yours. miy

Explore the idea behind miy
A connected workplace A notebook of ideas, business apps, data and servers joined by a single line CREATE A place for your work. CONNECT
YOUR IDEAS, CONNECTED.One place to build apps and bring work together.
01 / THE IDEAIt starts with your work.

Every company has
its own way of working.

Work stitched together in spreadsheets. Requests lost in chat.
Tools that never quite fit the way we work.

As AI makes app creation easier, even a small idea can become a tool of your own. miy connects building apps for your work with using them together. Add the apps you need, while keeping data and management connected within your company’s workspace.

SMALL APPS. REAL WORK.

Start with one everyday friction.

Examples of apps you could build

“That purchase request—
where does it stand?”

A request in chat, an entry in a spreadsheet, another follow-up. Bring the whole process, from request to approval, into one flow.

  1. Request what you need

    Keep the item, quantity, purpose and quote together.

  2. Review by your own rules

    Route each request to the right reviewer for its department and amount.

  3. See progress together

    See who reviewed it and how far it has progressed.

Your request forms, approval rules and statuses.

Concept examples of apps you could tailor to your work. Each app serves a different purpose, while data and permissions share a common foundation.

02 / FROM IDEA TO EVERYDAYBuild. Check. Run.

From an idea
to everyday work.

Help the apps you build with AI become part of real work.
Connect development, review and operations in one flow.

YOUR TOOLS. YOUR WAY.

Familiar tools.
Your way of working.

  • Claude Code
  • Codex
  • Gemini CLI
  • OpenCode
  • Cursor
  • Cline
  • Pi

Connect familiar AI tools to miy’s app structure and shared capabilities. The design lets you keep working with those same tools after deploying your apps.

Keep working with the AI you know
01 — BUILD WITH CONTEXT

Turn the way you work
into the apps you use.

What should be recorded? Who reviews it? When is the work done? People who know the work and those building the app define the flow together. Connect miy’s structure and guidance to familiar development tools to build the screens and features you need.

No need to start everything from scratch

Let miy handle shared capabilities such as sign-in and permissions, so you can focus on what your work needs.

A PLACE TO START.
Could we see all our
purchase requests here?
•••your editor + AI↗
miyYour work + shared app capabilities
Your company’s
first app
YOUR IDEAYOUR APP

Concept illustration for explanation. The actual product may look different.

03 / MORE OF YOUR WORK. LESS REPEAT. Different apps. Common ground.

Lay the groundwork once.
Build on it together.

Sign-in, data connections, familiar interfaces.
Build what makes your work different on a shared foundation.

EACH APP, EACH TIME

Starting over with every app

Purchasing

Screens · Rules

  • Sign-in
  • Data connections
  • UI components
  • Deploy settings
Purchase data

Assets

Screens · Rules

  • Sign-in
  • Data connections
  • UI components
  • Deploy settings
Asset data

Inspections

Screens · Rules

  • Sign-in
  • Data connections
  • UI components
  • Deploy settings
Inspection data

Rebuilding the same capabilities,
then reconciling different connections and experiences.

WITH MIY

Focus on what makes each app different

Purchasing

Screens · Rules

Purchase data

Assets

Screens · Rules

Asset data

Inspections

Screens · Rules

Inspection data
miy Shared platform foundation
  • Shared identity & access
  • Shared UI components
  • Approved data connections
  • Consistent deployment

Share the foundation,
while keeping each app’s data and permissions distinct.

Concept diagram of a reusable foundation. Each app’s data connections and business permissions are defined and validated separately.
01

Less repeated development.

Reuse shared identity and components instead of rebuilding the same capabilities from scratch.

02

Get to useful work sooner.

Spend less effort preparing and validating the foundation, and more time building and improving the work itself.

03

A familiar experience.

Consistent sign-in and interface behavior make each new app easier to learn.

04

Easier to hand over.

Carry maintenance and handovers forward with shared conventions and a clear change history.

And where do the apps run?
04 / A PLACE FOR YOUR APPSReady underneath.

Everything underneath.
One environment.

The runtime, data and operational tools your apps need.
Bring them together in a place that fits your company.

IN YOUR OFFICE IN THE CLOUD
Your on-premises workspaceYour own environment
App A
App B
Work AI
miy A shared foundation for work
Identity · AccessDeploy · OperateData connections
App dataFiles · DocumentsConnections · Access
Company network Approved network paths
Internal users · Systems
External workplaces

Install on company hardware and connect your apps and data through the company network.

YOUR APPS, IN YOUR ENVIRONMENT
01

Work together in one place.

Employees sign in to miy to use the apps and work AI they’re allowed to access. New apps join the same workspace.

02

More apps. One place to manage them.

See deployments, updates, runtime health and change history in one place. Reduce the need to prepare a separate operating foundation for every app.

03

Operations that fit your company.

Run it yourself or share responsibilities with a partner. Wherever it’s installed, your company decides who operates it and how much to delegate.

THE EVERYDAY ESSENTIALS

What used to be separate,
ready together.

A design that brings app infrastructure into one operating framework. Connect the capabilities you need, then track their health and changes together.

01Apps & data
Web server · HTTPS · RoutingApp runtimeDatabaseFile storage
02AI capabilities
Vector search · Document indexingLLM gateway Model connections · Policies · Usage
03Builds & jobs
Build · Validation environmentsSource · Build artifact storageBatch · Scheduled jobsJob queues
04Operations & protection
Shared identity · PermissionsSecrets · ConfigurationHealth · Logs · Resource monitoringBackup · Recovery

An example grouping of capabilities. The actual setup depends on the deployment environment and scope of use.

Design direction for automated operations

AI that understands operations
and follows through.

From environment setup and deployment to updates and incident response, within the goals, permissions and policies your company defines. The aim is an operations AI that reads the situation, plans the work and verifies the outcome.

Within your company’s goals, permissions and operating policies
  1. 01Observe

    Read logs, resources and app health

  2. 02Analyze & plan

    Assess causes and impact, then plan the work

  3. 03Configure & deploy

    Adjust settings and update apps and environments

  4. 04Verify

    Check health and progress against the goal

  5. 05 / IF NEEDEDRecover

    Use a recovery path suited to the data and backups

Concept cycle for autonomous operations AI. Its operating permissions are distinct from the role of conversational work AI.

Autonomous within its remit.

Authorized tasks proceed without waiting for approval each time. Requests beyond its permissions or policy boundaries stop and are brought to the person responsible.

Every action, visible.

Record the reason, target, changes and results of each task. The design lets operators follow progress and stop work in progress.

Recovery grounded in reality.

Check data changes, backup timing and version compatibility. Assess viable recovery paths, and hand over to a person if no safe path exists.

How does it connect to existing systems?
05 / YOUR SYSTEMS, CONNECTED. One connected way of working.

The systems you already use.
Part of the same flow.

Connect information across your ERP, CRM and collaboration tools through miy. Add shared business meaning to different data, so agents can find what they need and prepare the next step.

Design direction for system and agent connections

01 / EXISTING SYSTEMS

Existing systems

  • ERPPurchasing · Finance
  • CRMCustomers · Sales
  • CollaborationPeople · Approvals
  • Internal documents & dataResources · Records
miy Your connected work context
Connect the data and business capabilities you need

Business concepts & relationships

Ontology
A customer’s contract, orders under that contract, and the settlement linked to each order Signs Covers Links to Customer Contract Order Settlement

Different names across systems,
connected to the same entities and relationships.

Shared permissions · Data policies · Sources
02 / AGENT AT WORK

Autonomous work agent

  1. 01
    Find the right information

    Query the systems and information relevant to the question

  2. 02
    Follow the relationships

    Connect and analyze material from multiple sources

  3. 03
    Prepare the next step

    Propose an action with sources and planned changes

YOU DECIDE Your review · Final execution

Review the target and changes before you act.

Through miy’s permission checksExisting system capabilities · miy apps
Concept diagram of querying information and preparing work through miy while keeping source systems in place. Integrations are examples; connection scope and business relationships are defined around your systems and permissions.
01

Keep your systems.
Connect your work.

Build on the information and capabilities already in your systems. Keep those systems in place and connect them so people can find and use what they need through miy.

02

The same entities.
A shared context.

Connect different terms—such as a CRM customer and an ERP account—to common business concepts. A business ontology defines the meaning and relationships between customers, contracts and orders.

Bring connected work to your AI
06 / AI, WITH YOUR CONTEXTFrom an answer to a next step.

AI that knows your work.
From answers to action.

Connected information grounds the answer.
What you verify informs the next step.

  1. 01

    Find answers in your own material.

    Search connected systems and documents for material the user is allowed to access.

  2. 02

    See what the answer is based on.

    Show the sources used, so people can check the information before deciding what comes next.

  3. 03

    You decide when to act.

    Show the planned changes first. When the user reviews and executes them, permission checks run before changes are applied.

MIY / A WORKING CONVERSATIONIllustrative conversation
YOU

Please request one monitor for design work.

miy.

I’ve prepared a request following the equipment purchasing guide. Please review the details and submit it.

Source Equipment purchasing guide
PurchasingReview before submitting
Item / Quantity
Monitor / 1
Purpose
Design work

I review and make the final submission

In conversation or in an app. The same permissions and rules.
YOUR AI. OUR SHARED CONTEXT.

In the AI you know.
And inside miy.

Different places to use AI. One work context.
Connect your existing AI tools and miy’s built-in agent
to the same business data and capabilities.

TWO WAYS IN. ONE WORKPLACE. Connecting AI environments · Design concept
01 / THE AI YOU ALREADY USE

Your AI, as you know it.

Familiar AI tools such as Claude Code and Codex

Look up company information, analyze it and prepare the next step within your familiar conversations and workflows.

MCP · API · CLI The right connection for each tool
02 / INSIDE MIY

A built-in work agent.

Find relevant material, work through multiple steps of querying and analysis, and prepare the next task.

Models that fit your company

External LLM API / Local LLM / Sovereign LLM

Business tool access Shared permissions & policies
miy

One foundation for work

Connected systems & apps
Core systems · Internal resources · miy apps
Connected work context
Data · Business relationships · Ontology
Common rules throughout
User permissions · Data transfer policies · Activity records
Your review · Final execution

Once you review and execute the prepared action,
miy checks permissions before applying it to your work.

Connection methods and capabilities may vary by tool. Personal AI environments connect only to information and functions your company permits.

THE MODEL IS YOUR CHOICE.

Keep the work connected.
Choose your own models.

Choose the models for miy’s built-in agent
to match your environment and data policies.

01External LLM API
Connect external model services approved by your company.
02Local LLM
Connect models running in an environment your company operates.
03Sovereign LLM
Connect model environments that meet your data residency and operational control requirements.

When using external models, permitted information may be sent to that service. Information that must remain internal is designed to be handled in an approved internal model environment.

DESIGNED FOR AIDesigned to connect with AI CLI · MCP · API

From building an app to everyday work, the interfaces are designed to help AI find the context and capabilities it needs. Use the connection that fits each tool, with miy’s permissions and business rules applied throughout.

01CLI
Repeatable work. Consistent steps.

Connect project setup, checks, deployment and status inspection through commands. Extend this approach to recurring work through permitted commands and procedures.

02MCP
Give AI the context it needs.

Connect development guidance, approved business resources, data structures and available tools so AI can discover and use them.

03API
The same rules, from any entry point.

Connect business apps, external AI tools and miy’s own screens to the same capabilities. Apply common permissions and policies regardless of where a request starts.

miy checks access permissions across all connection paths. App development, operations and business data have distinct permissions, and only company-approved information is shared with AI.

07 / YOURS, BY DESIGN Yours, from the beginning.

Your data.
Your rules.

Where it lives. Who can see it. What it connects to.
Data sovereignty and security, considered from the start.
Another meaning of yoursat miy.

YOUR ENVIRONMENT

Where your data lives.

On-premises or in the cloud, in an independent environment you choose.
Your company sets the location and retention rules.

YOUR ACCESS

What people and apps can access.

Who can use which apps and resources, and what they can do.
Grant and revoke permissions by role. Your company also defines the access of external builders and operating partners.

YOUR AI POLICY

What you share with AI.

Define what AI can see and what can leave your environment.
Set the permissions needed by development AI, work AI and operations AI separately, with each designed to follow your data policies.

SECURITY, LAYER BY LAYER

From external access
to internal permissions.

Limit entry points, validate requests and check access scope. Layered defenses are designed to keep unauthorized access away from your work and data.

  1. 01 / REQUESTIncoming requests

    Users · Connected services

  2. 02 / ENTRYProtected entry points

    Public endpoints · HTTPS

  3. 03 / VERIFYIdentity & request checks

    User · Session · Origin

    Block forged or unauthenticated requests
  4. 04 / AUTHORIZEApp & data access checks

    Per-action permissions · Scope

    Deny out-of-scope access
  5. 05 / WORKAuthorized work runs

    Record access and activity

Concept flow illustrating access controls. HTTPS encrypts data in transit; request validation and permission checks are separate steps.
01

Open only the paths you need.

Limit direct exposure of internal databases and management functions, and maintain boundaries around each app’s data and runtime. Make secrets available only where they’re needed.

02

Protection continues in operation.

Keep access and activity logs and watch for anomalies. Treat security updates, backups and recovery procedures as part of everyday operations.

Alongside the shared security foundation, each app needs its own business-logic and permission validation, with security settings suited to the deployment environment.

MAKE IT YOURS.

It’s your work.
Make it yours.

Build the apps you need. Connect the work you’ve built.
Keep data and AI on your company’s terms.

A place for work that feels like you. miy.

Get in touch mc.joe@miy.works
Back to the beginning