OPEN OVERSKILLPublic starter

Build your own
AI app builder.

Start with a builder kit. Make it yours.
Give your users a place to create apps on Overskill.

MIT starter on GitHub. Hosted demo in preparation.

your builderILLUSTRATIVE BUILDERCreator workspace
Build something for your people.The experience is yours to shape.
Build a client portal for my coaching program. Add a resource library and session booking.

Give every creator a place to describe, refine, and publish their app.

  • Live build conversation
  • App preview in your interface
  • Publish and hand back the link
Your prompt goes here…
App previewDesktop / Mobile
Studio NorthOverview   Resources   Sessions
YOUR CLIENT PORTAL

A little structure.
A lot of progress.

Everything for your next chapter, in one place.

01 / RESOURCESThe getting-started guideYour next step starts here.
02 / SESSIONSMake time for what matters.Find your next session.
Built for your community
Your interface, from the first prompt to the published app.POWERED BY OVERSKILL

THREE WAYS TO BUILD ON OVERSKILL

Start with the kit.
Choose the help you need.

A complete starter, components for your existing product, or a bespoke partnership. Pick the route that fits what you’re building.

01 / SELF-SERVE KITStart here

Your own builder,
from a complete starter.

Clone the public starter, run the local demo, and make it your brand. Connect it to Overskill with approved partner credentials when you’re ready to validate live use.

Public source · Live partner access by approval

Explore the starter
02 / COMPONENTS + INTEGRATION

Add a builder to
the product you have.

Use the composer, build conversation, preview, and publish views inside your own interface. Shape the integration with your developers or an implementation team.

Pilot scope · Implementation help by arrangement

Explore the components
03 / BESPOKE PARTNERSHIP

A builder designed
around your platform.

For selected larger partners with deeper product requirements. Work through a custom branded experience, account mapping, integrations, and launch together.

Selective · Scope and terms agreed individually

Discuss a partnership ↗

THE SELF-SERVE STARTER

Get the kit.
Make it your builder.

A frontend, reusable UI, and a server adapter built around one journey: prompt, preview, publish. Your brand and audience guide the rest.

What’s available today

The starter repository is public under the MIT license. Clone the source, run the local demo, and adapt it for your audience.

Starter repository: github.com/OverskillDev/open-overskill · Public source.

Source access is open. Live partner credentials and onboarding require approval.

  1. 01

    Explore the integration.

    See how Overskill’s API connects app creation, previews, and publishing. Read the partner API documentation to understand how the starter connects to the managed service.

  2. 02

    Run and adapt the starter.

    Clone the public repository and try its local demo with simulated accounts and credits. Adapt the provided builder interface and server adapter. Set your name, styling, and starter prompts for the people you serve.

  3. 03

    Connect accounts. Test a complete build.

    Use approved Overskill access, keep credentials on your server, and connect each creator to their own workspace. Stage one uses existing Overskill credit packs for that creator’s workspace. Validate customer onboarding and merchant/payment setup before accepting payments. Take a prompt through preview and publishing before inviting your users.

OPEN WHERE YOU BUILD. MANAGED WHERE IT RUNS.

Make the experience yours.
Build on Overskill’s engine.

The pilot brings an adaptable builder interface to Overskill’s partner API. The generation engine stays a managed Overskill service.

YOUR BUILDER / PUBLIC STARTER

The part your users see.

  • Builder frontendYour name, design, onboarding, and navigation.
  • Reusable componentsPrompt, conversation, preview, and publish views.
  • Server adapterConnect your authenticated users to Overskill’s API.

The starter frontend, components, and server adapter are public under the MIT license.

OVERSKILL / MANAGED SERVICES

The engine behind the experience.

  • Generation orchestrationTurn requests and revisions into generated apps.
  • App runtime and publishingPreview, deploy, and return the app to your product.
  • Credits and billingUsage stays on Overskill’s managed service.

These services remain proprietary and are not part of the open release.

YOUR USERSYour branded interface
YOUR SERVERAuthenticated adapter
OVERSKILLGenerate · preview · publish

Partner credentials stay on your server. Creator access is scoped through the partner integration. Overskill manages the model keys; you and your users do not bring your own AI provider keys.

LESS ASSEMBLY. MORE OF YOUR PRODUCT.

Start with the pieces
a builder needs.

Keep your existing product and use the builder pieces it needs. The pilot will help define the component interfaces and the integration work your team can hand off.

01 / COMPOSER

A place to start.

Give users a prompt box, useful starting ideas, and a clear next action.

02 / BUILD CONVERSATION

Keep the work visible.

Bring the build conversation and progress into your own interface.

03 / PREVIEW

See what’s taking shape.

Put the app preview beside the conversation so users can review their work.

04 / PUBLISH HANDOFF

Give the app a next step.

Return a published link or approved embed to your product when deployment completes.

NEED HELP CONNECTING THE PIECES?

Bring your team. Or scope the work with one.

Components reduce the interface work; your product still needs account mapping, permissions, and a tested handoff. We can discuss a partially done-for-you integration and whether an implementation team is the right fit. Team availability, scope, and terms are agreed separately.

Ask about integration help ↗

A FEW CLEAR ANSWERS

What “open” means here.

Is the whole Overskill platform open source?

The public MIT starter includes the builder frontend, reusable interface components, and server adapter. Overskill’s generation orchestration, managed runtime, and billing services remain proprietary.

Can I get started without a call?

Yes. The public GitHub repository is available to clone and adapt, and the local demo uses simulated accounts and credits. Live partner credentials, customer onboarding, and merchant/payment setup still require approval and validation. The hosted example and automatic account enrollment are not available yet.

Can I use my own brand and interface?

Yes, shaping the builder around your brand is the purpose of the kit. The components route fits an existing product; bespoke partnerships address deeper requirements for selected larger platforms. Full white-label packaging, attribution, and commercial terms need an agreement and are not an automatic entitlement of starter access.

Will someone build the integration for me?

The kit is designed for people who want to do the setup themselves. The components route can include implementation help, scoped with your team or an implementation team. Bespoke partnerships involve a deeper engagement. Neither service is included automatically with starter access.

Who pays for the apps my users build?

Stage one uses existing Overskill credit packs. Each creator buys credits for their own Overskill team (workspace), and their builds use that workspace’s credits. The hosted example is not open for paid use yet. Operator-funded accounts, custom pricing, and partner commissions are future options to evaluate; they are not included in the stage-one pilot.

Does each creator need their own workspace?

Yes. Stage one keeps each creator’s apps, credits, and permissions in their own Overskill team (workspace). The partner integration maps your authenticated users to those workspaces with scoped API access. Partner access and live onboarding require approval; your partner key stays on your server.

Can generated apps use my product’s live data?

Describe the data your app needs and how users should authorize access. Runtime access to a partner’s data is a separate integration to scope and validate; adding context to a generation request does not by itself create that connection.

Where can I explore the existing API and MCP?

Start with the partner API documentation for the API, or connect through MCP for an agent workflow. Partner provisioning requires approved access. The public starter demonstrates the integration; live onboarding and payments need separate approval and validation.

OPEN OVERSKILL / START WITH THE KIT

Your audience.
Your app builder.

Explore the starter first. Add integration help when your product needs it.

Start with the public MIT source. Live partner access requires approval.