{
  "id": "osc-stack-plan-own-ai-app",
  "job": "When you build an app with your own AI coding tool, have the OSC architect pick open-source services for it, then provision them and run the app for you on OSC, so there is no lock-in and the app and its data are hosted in Sweden.",
  "aliases": [
    "build an app with my own ai on open source",
    "which open source services should my ai-built app use",
    "run my ai-built app for me without lock-in",
    "host my ai-built app in sweden"
  ],
  "distinctFrom": [
    {
      "stack": "provision-agent-backend",
      "difference": "That stack only provisions the database and storage, for an app that runs outside OSC. This one runs the app on OSC, so it hands off to deploy-agent-written-app instead; use provision-agent-backend in place of step 2 only if you run the app elsewhere."
    },
    {
      "stack": "deploy-agent-written-app",
      "difference": "That stack provisions the database and storage and runs the agent's code as a My App. This one adds the planning step before it and hands off to it by id, without repeating its steps."
    }
  ],
  "inputs": [
    {
      "protocol": "MCP",
      "source": "your own AI tool (Claude Code, Codex, Cursor or any MCP client) connected to https://mcp.osaas.io/mcp"
    },
    {
      "protocol": "natural language",
      "source": "a plain description of the app: what it stores, who signs in, what files it keeps"
    }
  ],
  "outputs": [
    {
      "protocol": "plan",
      "consumer": "your AI tool",
      "content": "a list of real OSC serviceIds for the app (for example birme-osc-postgresql, minio-minio, eyevinn-web-runner) and the order to create them in",
      "example": "ask-osc-architect, read 2026-10-12, for a recipe-sharing site with accounts, a relational database and image uploads, returned eyevinn-web-runner (the app), birme-osc-postgresql (database), minio-minio (uploads) and optional valkey-io-valkey"
    },
    {
      "protocol": "hosting",
      "where": "OSC's primary infrastructure is Elastx in Stockholm, a Swedish-owned provider, and the applications you deploy and the data they store are hosted in Sweden. Some supporting functions rely on providers that operate outside the EU/EEA, such as payment processing, optional third-party sign-in and our AI features; the current list, and the transfer safeguard we rely on for each, is at www.osaas.io/subprocessors. If your own application or a service you configure calls a third-party API, that data goes wherever that provider operates, and it is your choice whether it does.",
      "source": "https://www.osaas.io/about (FAQ: Where is OSC hosted?), read 2026-10-12"
    },
    {
      "protocol": "exit",
      "howToLeave": "every service in the plan is unmodified open source; the app's code stays in your own Git repository and each service can be run yourself on any infrastructure"
    }
  ],
  "recommendedPath": {
    "chain": [
      {
        "step": 1,
        "role": "plan the app on open source",
        "mcpTool": "ask-osc-architect",
        "requiredInput": ["question or requirements"],
        "note": "Read-only and idempotent (tool annotations read 2026-10-12). Describe the app in plain words. The architect answers from the live catalog with real serviceIds; it creates nothing. The app description you send is processed by a third-party AI model provider in the United States (Anthropic or OpenAI), as listed on https://www.osaas.io/subprocessors (read 2026-10-12); do not put secrets in it."
      },
      {
        "step": 2,
        "role": "provision the services the plan names and run the app for you",
        "handoffTo": "https://www.osaas.io/stacks/deploy-agent-written-app.json",
        "note": "Follow that stack from its step 1: it creates the database and storage, the parameter store, and the My App, then waits until the app answers. Do not also run provision-agent-backend, or the database and storage are created twice."
      }
    ]
  },
  "cost": {
    "planningStep": "ask-osc-architect creates no service instance, so it adds no tokens/day of its own (no instance to estimate). Running cost comes from the services created in step 2; see the deploy-agent-written-app cost block.",
    "pricingSource": "https://www.osaas.io/pricing"
  },
  "configSurface": {
    "servicesInChain": 0,
    "mcpToolsInChain": 1,
    "totalRequiredFieldsAcrossChain": 1,
    "sensitiveFields": [],
    "note": "The planning step takes one free-text input (question or requirements) and creates no instance. Every service field is set in the deploy-agent-written-app stack this one hands off to; see its configSurface."
  },
  "setup": {
    "codeRequired": false
  },
  "servicesVerifiedLive": {
    "date": "2026-10-12",
    "method": "osc_search_tools on ask-osc-architect (schema and annotations) and one live ask-osc-architect call via osc_call_tool, 2026-10-12"
  },
  "gateCheck": {
    "gatedServiceId": "eyevinn-just-go-live",
    "usesGatedService": false,
    "note": "This stack does not name or link eyevinn-just-go-live; the P3 gate does not bind it."
  },
  "verifiedOn": "2026-10-12",
  "publishedAt": "https://www.osaas.io/for-builders",
  "descriptorUrl": "https://www.osaas.io/stacks/plan-own-ai-app.json"
}
