Documentation · Updated 8 November 2026

Use and manage your app

A practical guide for customers, app administrators and delivery partners: build and manage business apps, websites, automations and AI agents, connect services, and track usage, costs and results.

On this page
  1. Getting access
  2. What you can build
  3. How Chromoly builds
  4. Plan and build
  5. Design in Chromoly
  6. Penpot and Google sign-in
  7. From design to a working product
  8. Draft, preview and publish
  9. Customer review and approval
  10. Custom domains and domain purchases
  11. Changes, dependency map and history
  12. The app blueprint
  13. Records, imports and exports
  14. Charts, dates and time zones
  15. Appearance, websites and portfolios
  16. App users, administrators and settings
  17. Bookings and payments
  18. Workflows and automations
  19. AI agents inside apps
  20. AI processing and audit
  21. AI keys and spending
  22. Connect email, Slack and webhooks
  23. Whiteboards, documents and voice
  24. External AI clients and MCP
  25. MCP proposals and owner notifications
  26. Managed service, partners and credits
  27. Partner workspace
  28. Hosting and maintenance
  29. Data and access
  30. Exports, repository access and handover
  31. Troubleshooting and support
  32. Language and regional settings
  33. Larger builds and recovery
  34. Key terms

Features depend on your app, permissions and configured environment. Chromoly and authorised partners handle the builder; customers work in their delivered apps. Contact hello@chromoly.io for access or help.

1. Getting access

Chromoly is open for business, with managed service for businesses and an invitation-only partner tier. We agree the scope, hosting, maintenance, usage and support responsibilities with you. There is no public platform signup. Use Log in on the website if you already have access, or contact hello@chromoly.io to get started.

There are three separate invitations:

Use the email address that received your invitation. Google sign-in, where offered, authenticates your account; it does not grant an uninvited account access. Contact your app owner if an invitation has expired or was sent to another address. Check your junk folder if an expected invitation is missing.

2. What you can build

Chromoly builds internal tools such as CRMs, customer portals, booking systems, dashboards, invoice and approval flows, and onboarding tools. These can include configured automations and useful app-specific AI agents.

Websites focus on a business, its services, pages and calls to action. Portfolios focus on a person or studio, projects, case studies and visual work. Describe which you need: they are separate design briefs, not one fixed template. Layout, typography, color, imagery and supported effects can vary. Functional integrations, booking and forms still need setup and testing.

Ask for the features your process needs. An agent is not added merely because an app was built with AI. Games, native mobile apps and large consumer platforms are outside the standard delivery scope. Optional gamification can add points, achievements and progress to business apps.

3. How Chromoly builds

AI interprets your brief and proposes a structured blueprint. Chromoly validates it and assembles the app from shared, human-built components and supported server capabilities. The dependency map records relationships between pages, data, actions and workflows.

Structured builds show three progress steps: Planning, Building and testing, and Saving app. Building and testing includes supported behavior and interface checks, with bounded repair attempts that must preserve protected requirements. A blocked blueprint is not replaced with unrestricted generated code. Existing apps using the earlier isolated backend-code runtime remain supported. Passing the checks does not replace testing your actual business process and connected services.

4. Plan and build

Builder instructions are for Chromoly's delivery team and authorised partners. App users normally work directly in the delivered app.

  1. Describe the audience, records, actions and desired outcome. Include integrations, access rules, language, currency, reporting time zone and design direction.
  2. Use Plan to clarify requirements. Read the structured draft below the conversation; the chat reply is only a short introduction. Plans are intentionally concise but retain key requirements and assumptions.
  3. Revise the plan, then choose Use this plan in Build. Planning alone does not create or publish an app.
  4. Review the displayed credit price before confirming the build. Test the resulting preview and configured services.

English and Swedish prompts are supported. Ask explicitly for demonstration data; apps otherwise start with empty records. A browser-saved planning draft is not cross-device sync. If planning or building stops, follow the displayed recovery action or contact support with the build reference. Keep the requested features when reporting a validation failure; a failed check does not mean you need to remove requirements.

Example: “Build a Swedish request tracker for our operations team. Staff submit requests, managers assign owners, and the dashboard shows overdue work and monthly completions. Suggest priorities with AI for review. Use Europe/Stockholm for reporting.”

5. Design an app, website or portfolio

Design lets you arrange the interface before building the working product. Open Design beside Build and Plan in the builder. Choose Design in Chromoly for native components or Use a Penpot design for a Penpot file.

Design access is for approved partners, designers and platform administrators. Designer access is granted by Chromoly; changing your profile title does not enable it. If Design is missing, check that you are signed in with the approved account and contact support.

Design in Chromoly

  1. Choose New app layout, New website or New portfolio. New designs start with an empty canvas. Websites and portfolios default to Custom / From scratch.
  2. Enter a Design name and describe What is this layout for? The name is required for saving.
  3. Add blocks from the library. Select a block in Page structure to change its content, layout and supported properties. Use grid, split or stack layouts to place blocks beside each other or vertically.
  4. Add pages and connect buttons or navigation to those pages. Choose the home page and review URL names.
  5. Set appearance and supported effects. Review desktop and mobile views, then use the full-layout preview to open the design in a new window.
  6. Choose Save design to keep it in your private library, or Save and continue to prompt to save and attach it to Build.

The native editor uses your Chromoly account; a Penpot account is not required. Saved library designs can be reused without changing the original copy.

Blank canvas and optional templates

New designs and newly added website or portfolio pages start empty. Existing saved designs keep their content. Website directions are optional starting layouts: choosing one replaces the current page's blocks and appearance. Undo restores the previous design. Choosing Custom / From scratch clears the active page while keeping its appearance settings.

These starting choices apply to Design. They do not reset existing apps or change the defaults in Customize or ordinary prompted builds. A starting layout is a supported composition, not a promise that every original designer asset or effect is reproduced exactly.

Pages and reusable components

A design supports up to eight pages. Add, duplicate, rename, reorder, choose the home page or remove a page. Page links use stable references, so changing a page's URL name keeps its links connected. Removing a page clears links that targeted it; review navigation after removal.

Compose reusable visual components from supported blocks and save them in your private library. You can store up to 25 designs. Arbitrary React packages and executable component code cannot be pasted into the native library.

Colors, layout and effects

Use the appearance controls for available colors, typography, backgrounds, spacing and navigation. Color fields accept a six-digit hex value such as #2457FF; Reset removes the override. Background, surface and text overrides for app layouts are available in Design.

For websites and portfolios, expand Effects · motion, hover and scroll. Controls include motion, hover, section entrance, scroll, galleries, image trails, ticker style and motion, seal and illustration motion, and floating contact. Choose Off to disable a supported effect. Effects depend on the selected blocks and presentation; an image trail needs appropriate images, for example. The static design preview does not animate these effects. Review them in the generated preview before publication.

6. Use a Penpot design

Penpot provides layers, assets, reusable component instances, tokens and Design, Prototype and Inspect tools. Open design canvas opens the editor inside Chromoly. Review for Build returns to the import flow; Open separately is available if you prefer another tab.

Sign in with Chromoly or Google

  1. In the canvas toolbar, choose Create account / Google sign-in ↗, or select Chromoly / Google on Penpot's sign-in screen.
  2. Complete Sign in with Google outside the embedded canvas, using your approved Chromoly account.
  3. Choose Continue to Penpot to confirm access. Your first approved sign-in creates your own Penpot workspace.
  4. Return to Chromoly. If the canvas still shows the sign-in screen, choose Reload canvas after sign-in.

Access requires an active account, accepted platform terms, a confirmed email address, and approved partner/designer or administrator access. Public password signup is closed. Your workspace is private; signing in does not share other teams' files or grant Penpot administrator rights. Google sign-in authenticates you; it does not connect your Gmail mailbox. Password recovery email is not configured for this workspace; use Chromoly / Google for the supported sign-in flow.

If you see Open secure sign-in in a new tab ↗, follow that link and complete the steps in the new tab. Google sign-in cannot run inside the embedded canvas. Do not share sign-in links containing private state or tokens.

Import and review

  1. Save the Penpot file. Use one top-level board for each output page; separate desktop and mobile boards are not automatically combined.
  2. Choose Review for Build, then select App, Website or Portfolio.
  3. Paste your Penpot file link. In Penpot, open Your account → Access tokens and create a token with a short expiry. Paste it only into Penpot access token, then choose Find boards.
  4. Select the boards, set page names and unique URL paths, and arrange the home page first. Copy images only when you want that artwork to become public app assets. Choose supported effects for websites and portfolios.
  5. Import and review every page, including text, images, layout, navigation and the reported limitations. Optional Inspect HTML/CSS is reference material and is never executed.
  6. Choose Use design in Build, review the attached reference and add the behavior you need.

The import carries selected layers, source text, geometry, resolved styles, typography, gradients, shadows, supported blur, flex/grid metadata, component references, active design tokens and click links between selected boards. Unsupported vector artwork, masks, mixed text styles, background blur and other prototype actions are reported for review. The builder recreates the design with supported application components; importing is not a pixel-perfect code conversion.

The access token is cleared after import and is not saved in the design, prompt, browser storage or database. Google sign-in does not replace the import token. Importing reads the source file without changing it. Save changes in Penpot and explicitly reimport to refresh the snapshot; there is no live synchronization.

Images, privacy and size limits

Image copying is optional. Only use images you are permitted to publish. Private documents and confidential screenshots do not belong in public site imagery. Supported static PNG, JPEG and WebP artwork is converted to WebP with metadata removed. Missing or unsupported artwork is reported; inspect the result before building.

Penpot imports support up to eight boards, 250 layers in total, 80 active tokens and 12 distinct images. Native compositions support up to 50 blocks, six levels and a 5,000-character tree. The overall Build design reference has an 8,000-character limit, so a complex design can reach that limit before its page or layer maximum. Oversized designs show an error instead of silently omitting pages. Simplify the reference before trying again.

7. From design to a working product

Saving or attaching a design does not generate or publish an app. Build can infer ordinary forms, lists and navigation from the design and its purpose. You do not need to prompt every visual detail again. Describe the business rules that matter: which records to save, who can access them, which services to connect and what an AI agent may do.

For example: “Turn this customer portal design into a working app. Save customer requests, let staff assign owners and add an AI assistant that drafts replies for review.”

Payments, permissions, destructive actions, sending messages and agent side effects need explicit requirements and configuration. Review the displayed credit quote, build, test the preview and publish separately. You can add workflows later through Edit with AI. A design reference cannot override permissions or bypass build checks.

Design previews are read-only. Example chart/table content is illustrative and never creates app records. A generated app preview can use real records and connected services: test with synthetic data and destinations you control.

Common problems

See the full user guide for testing, publication, permissions and support. Contact hello@chromoly.io without including passwords, API keys or private sign-in links.

8. Draft, preview and publish

In the owner’s standalone preview, choose Edit & publish to return to the app editor. Saving an edit creates a draft version. The live app continues using its published version until a separate publication succeeds. Restoring a version also creates a draft.

A failed publication does not activate a new app version. Contact support if the state is unclear before retrying. Unpublish app stops hosting and background execution while retaining saved app data. Hosting cleanup must finish before its live slot is released; reconnect custom domains when publishing again.

An unpublished app's old hosting deployment may have been deleted, so its old publishing logs are no longer available. The current log dialog can still show “temporarily unavailable” in this case; repeated retries cannot restore deleted logs.

9. Customer review and approval

Customer review is optional. The app owner opens Publication settings in the publishing panel to reach Publication & ownership. Invite the customer's email as a reviewer, select that reviewer and request review of the current draft.

  1. The customer follows the review email and signs in with a single-use email link sent to the invited address. Review sign-in works for websites and portfolios even when the app itself has no login.
  2. Review the exact version, change summary, affected items and presentation preview. Protected app features are placeholders in this preview; it does not execute workflows or expose live records.
  3. Choose approve or reject. Approval is bound to that version. Further edits require a new review.
  4. Use the return-to-app link after the decision. The owner then publishes the approved version separately.

Inviting a reviewer does not block publication. Enable Require customer approval before publication in the app rules to require that customer’s approval of the exact version. When the rule is off, an authorized publisher can publish directly. When it is on, the owner cannot approve on the customer’s behalf.

Review sign-in links expire after 30 minutes, and review sessions after one hour. Request a fresh link if needed. These limits are separate from MCP proposal expiry.

10. Custom domains and domain purchases

Open Custom domain in the editor’s publishing controls before or after publication. Save and verify an existing domain while the app is unpublished; it waits for publication before hosting activates. Domain registration and DNS setup are separate steps.

Connect existing domain: enter a hostname, such as example.com or app.example.com, without https:// or a path. Add the exact ownership TXT and hosting DNS records shown, then use Check connection until the domain is connected and HTTPS is ready. Connect www separately if needed; redirects and wildcard domains are not automatic.

Your DNS provider is the service managing your domain's nameservers. Your application host is not necessarily your DNS provider. Use the DNS management link where offered and confirm which provider hosts your zone. Some providers append the domain to record names automatically.

Buy domain: the platform app owner checks availability and USD registration/renewal pricing, enters the customer's registrant details, then chooses Continue to payment. The payer enters their own payment details in Stripe's hosted Checkout and confirms the final amount including applicable tax. Chromoly registers the domain only after verifying payment. Automatic renewal is off.

DNS and certificate setup can take time. If registration succeeded but connection is pending, check the saved order instead of buying again. If the purchase outcome is uncertain, contact support before another attempt. Complete any registrant verification email.

Only the app owner can connect or disconnect domains. Disconnecting does not cancel domain registration or auto-renew, and does not delete your DNS records. Registration, renewals and hosting are separate responsibilities; agree ownership and billing with the delivery team.

11. Changes, dependency map and history

Use the editor's Dependency map to see the app's pages, tables, fields, API actions, workflows and integrations. Select an item, search the tree or use the relationship list. Viewing the map does not change the app or use AI credits.

Change reviews show additions, removals and affected dependencies. Labels such as Safe, Affected and Breaking describe static analysis, not a guarantee that a change works. Dynamic code and external services may have effects the map cannot see. Test important paths before publication.

History shows saved versions and lets you compare or restore them. Restoring creates a draft; it does not undo changed records, sent messages, payments or other external effects. Appearance preferences and ordinary record updates are operational settings/data, not code releases.

12. The app blueprint

AppSpec describes pages, data, APIs and workflows. It is the app's structured model, not its business records. The dependency map helps explain the impact of a proposed model change. Keep the scope focused on the work your users need to do.

13. Records, imports and exports

Use forms to add records and supported table controls for CSV import/export. Review field mappings and validation before saving. Charts and totals use saved records, not invented activity.

Supported tables can extract records from text-based PDFs for review and export loaded, filtered rows as a PDF report. Scanned PDFs need OCR, which is not included in that import flow. A table PDF is not a full dashboard export. Check extracted values before saving; exporting visible rows is not a full app handover.

14. Charts, dates and time zones

Supported charts include category breakdowns and trends over time. Trends need dated records or stored snapshots; an empty month can show zero without inventing data. Reports configured as rolling monthly series advance automatically. A fixed historical report may need an edit.

Set your profile time zone and the app's reporting time zone separately. Booking availability uses the booking workspace's time zone. Interface language does not change currencies or time zones.

15. Appearance, websites and portfolios

Specify a visual direction when planning, including brand colors, typography, layout and images. Owners can configure the app's name, logo and supported appearance settings. App default, Light and Dark have different purposes; use the controls available in your app.

For websites and portfolios, the supported content editor saves draft content. Review & publish opens the publication flow; it does not silently publish the content. Review mobile layout, image crops, readable button labels, links and forms before launch.

Uploaded public-site images are public assets. Do not upload private documents as website imagery. Older exported frontends may need republishing to receive shared UI improvements.

16. App users, administrators and settings

If you already have a Chromoly platform account, open Dashboard → Shared with me to find app memberships for your verified sign-in email. Pending invitations and unpublished apps are labelled. Open the app and use its normal sign-in; membership does not grant builder or platform-admin access. An app invitation does not create a platform account.

Chromoly administrators use Managed apps to work on an explicitly assigned customer or partner app with their own account. This workspace is not visible to partners or ordinary members. The grant defines access; optional publication permission still requires approval of the exact version. Customer groups in Partner workspace organise apps; they do not transfer ownership or grant access.

The owner can invite internal colleagues in App settings → General → Users and sign-in, choose Administrator, or update an existing internal user's role. Administrators can invite ordinary coworkers and external clients; only the owner assigns administrators. External clients cannot be administrators.

Available settings depend on the app’s features and your permissions.

Inside the app: App settings contains General and Notifications, plus Documents, Automations and Connections when the app uses those capabilities. An owner also sees Gamification when the module is enabled. App administrators keep their permitted operational controls; server permissions still apply to every action.

In Chromoly: owners and authorised delivery partners use Manage app in Chromoly to open app management in a new tab. Setup, publication, AI settings, webhooks and audit views live here. Website content and analytics are shown only for websites and portfolios where those features are available. An app administrator role alone does not grant access to platform management.

Notifications are on by default: in-app notices and critical failure or unconfirmed-run emails do not need an additional channel preference. Email delivery still depends on a working sender. Open Notifications → Additional delivery channels to configure optional email or Slack deliveries. Saved preferences are preserved; opening settings does not connect a service or send a test.

Where agents are available, administrators can inspect their setup, team access, schedules, history, proposals and reports. Creation, activation, execution, approvals, budget changes and deletion remain owner-only. Ordinary members need explicit agent access.

App administration does not grant platform billing, builder ownership or access to another app. A customer reviewer is a separate role. If a tab is missing, check that the invitation was accepted, the user is enabled with the intended role, and the app frontend is current.

17. Bookings and payments

Booking apps need services, availability, durations, prices and a booking time zone. Review the public page before enabling bookings. Customer email and owner notifications require their own setup.

Supported payment flows use the owner's fixed-price Stripe Payment Links and a configured, signed Stripe webhook. Test the booking, payment email and confirmation with matching amount, currency and test/live mode. A successful browser return alone does not mark a booking paid. Refunds, disputes and tax decisions stay in Stripe; cancelling a booking does not automatically refund it.

18. Workflows and automations

Open App settings → Automations, or select a workflow in the dependency map and open its details. The controls include Trigger, Data mapping, Test, Email draft, Schedule and Run history.

Choose a supported app action, incoming webhook event or schedule as the trigger. Map required data, set the time zone for schedules, and use the test controls before enabling work. A trigger must match an action or event that actually exists in the app.

Save paused stores settings without activating the automation. Save and enable is available only when prerequisites are met. If the panel says to enable the workflow in the app editor first, ask the owner/delivery team to update its definition and publish it as needed. A saved schedule alone is not proof that the scheduling worker is running; verify a due run before relying on it.

Use run history for step outcomes and failures. A simulation is not proof of external delivery. If an email or webhook timed out, check the provider before retrying: the action may already have completed. Cancellation cannot recall an external action already sent.

Optional gamification for business apps

Add points, achievements and progress to work such as a sales contest, employee onboarding or training. Gamification is an optional module, off by default. Ask for it explicitly when building, or enable it as the app owner. The planner must not add it on its own. It complements business workflows; it is not a game builder.

Gamification is available as an optional add-on. Open Manage app in Chromoly → Gamification, enable only the parts you need, and review the award rules, visibility and time zone. Saving creates a draft version; changes take effect after review and publication. For example, onboarding can use a progress bar and badges without a public leaderboard.

Points come from declared rules and an award history, not directly edited balances. Retrying the same event does not award it twice. Choose who can see rankings: everyone in the app, the relevant team, or only each person’s own statistics. Participants can choose a display alias and opt out of public rankings; email addresses are not used as leaderboard names.

Milestone notifications and celebrations are optional. The module uses the existing notification system, and animations respect reduced-motion preferences. Turning gamification off hides its interface and stops new awards after publication, while keeping its history. Deleting history is a separate owner action; restoring a blueprint does not erase awarded points or recall messages already sent.

Test award rules and permissions with controlled test data before use. Mini-games, custom animations and requirements beyond the available building blocks are marked as needing development.

19. AI agents inside apps

AI agents are available inside apps. Owners configure their purpose, permitted tools and data, team access, budgets, triggers and approval rules. Review proposals and run history before enabling recurring work. AI use is funded through credits or a supported BYOK connection.

The app owner can open AI agents even before creating an agent. Other members see only agents and actions their permissions allow. A relevant suggestion is a starting point, not an active agent. AI assistants have their own sidebar destination when included in the app; an assistant and an autonomous agent are different features.

The owner sets up agents inside the app: review the purpose, allowed tools/data, team access, budget, triggers and approval rules. A suggestion does not activate or run an agent. Test a small task first and inspect the run history and proposals before enabling recurring work.

Members see only agents shared with them. Agent proposals, MCP approvals and customer publication reviews are separate flows. Do not assume that connecting a service or accepting a build plan gives an agent permission to send messages or change records.

20. AI processing and audit

In App settings → Documents, the owner or an authorised app administrator can save readable PDF text and enable Share with users’ AI for each document. Documents start private. Sharing lets signed-in app members ask the configured assistant about selected documents, with source references. Check answers against the sources. Turning sharing off stops its use in future questions; it does not erase answers already returned.

Website research is optional for relevant assistants. Where enabled, choose Add a website source, enter a public HTTPS page and submit a question. It reads that page’s text; it is not a general search engine, crawler or access to private websites. Ordinary links are not automatically visited.

EU processing is the default for new builds and in-app AI; existing saved processing choices are preserved. The configured EU route uses Berget. Check the model selector and processing details for the models available in your environment. Global processing is a separate choice and may use providers outside the EU. An unavailable EU route must not silently switch to Global.

Open Manage app in Chromoly → AI settings for app AI configuration. AI activity & audit records provider/model, timing, outcome and available usage metadata; it is not a transcript of private reasoning. Review AI-generated calculations, extracted records and drafts before relying on them.

Database location, AI processing and external integrations are separate data flows. Connecting an external AI client or service does not make that service EU-hosted.

21. AI keys and spending

In Manage app in Chromoly → AI settings, the owner or an authorised managed-app administrator can configure a supported provider key for app and automation AI. Agents have their own funding and run-budget controls. BYOK does not pay for builds, edits, hosting or other services. A failed or unavailable key does not silently switch to platform credits. Never paste keys into prompts, email or support screenshots.

Only use bring-your-own-key controls if they are available for your account and supported provider. Adding a key does not remove hosting limits, access controls or the need to review that provider's processing terms. Ask the delivery team before choosing a provider for sensitive data. Never paste API keys into a prompt or email.

22. Connect email, Slack and webhooks

Use Manage app in Chromoly → Connections to configure services. Apps that use connections also offer the relevant Connections panel inside App settings. Google sign-in is account authentication; it does not connect a Gmail mailbox. A service mentioned in a prompt is not automatically connected.

For customer email, the owner connects their own Resend account, enters a sending-access API key and an address on a domain verified in Resend. Saving does not send email or prove that delivery works. Test the actual sending flow with an address you control. Platform invitations and owner notifications use a separate sending setup. Check junk folders; provider acceptance is not inbox delivery.

For Slack, the owner completes the available connection flow, chooses the destination channel and explicitly tests it. For incoming webhooks, enable the endpoint under Manage app in Chromoly → Webhooks, copy its URL and one-time secret into the sending service, then send a test event. Receiving an event alone does not update business tables: configure the corresponding workflow. Outgoing webhooks need a configured HTTPS destination and an explicit test or enabled event.

Keep secrets in credential fields. Check destination, authentication and provider history before enabling recurring or customer-facing actions.

23. Whiteboards, shared documents and voice

Apps can include a Studio for shared text documents and Excalidraw whiteboards when configured. All authenticated app members can read these shared documents; owners, administrators and editors can edit them. This workspace does not provide selected-member or per-record document sharing.

Text documents support simultaneous editing and persistent synchronization. Whiteboards use explicit Save drawing, with revision checks to prevent silently overwriting another save. They do not use simultaneous drawing collaboration. If a save conflicts, preserve your changes before reloading the saved drawing.

Where the microphone is offered in a prompt or AI composer, start recording, stop and review the transcribed text before submitting. A transcription workspace can also process supported audio/video files or explicitly selected meeting-tab audio. Browser support and the displayed duration, size and account quota limits apply. Keep the tab open during processing. Tab-audio capture is not a meeting bot, and no screen video is transmitted.

Transcripts are editable. Transcription alone does not send the prompt, save an app record or run an agent. Saving a transcript requires a configured save action. Get the participants' permission before recording a meeting.

24. External AI clients and MCP

Chromoly has two different MCP flows:

An app connection can read granted tables/fields, search records and saved PDF text, use permitted chart context, propose record changes, request supported app actions and workflow starts, and inspect permitted runs. Nothing is granted by default. UI-only access does not grant record access. Direct record changes do not run business-action hooks; use the app's supported action for a business operation.

UI proposals can change supported presentation for apps, websites and portfolios. They cannot change backend logic, schemas, permissions, functional bindings or arbitrary source code. Approved presentation edits become drafts and still need publication.

For EU apps, each external connection needs separate owner consent: the external client's processing locations and terms are independent of the app's EU mode. A connection lasts for the selected period (7, 30 or 90 days in the UI). Version changes can invalidate it; reconnect and review permissions when prompted.

For builder Tools, review selected resource text before Use in Plan and Build. External tool calls require Review tool call, then Confirm and run tool. They may change data at that external service. Reviewed results provide build context, not a permanent integration in the generated app. Reloading clears connection credentials; previously submitted context can remain in the plan/history.

25. MCP proposals and owner notifications

Record changes, app actions and workflow controls requested through MCP require owner approval. The AI client cannot approve its own request, and an app administrator is not the platform owner.

Owners can open the direct review link in the notification/email or go to AI client connections → Review requested changes. Sign in as the owner, inspect the exact request and any presentation comparison, then approve or reject. Opening the link does not execute anything. Email delivery depends on the configured sender; check the request list if no email arrives.

New proposals remain actionable for seven days, unless invalidated sooner by changes, expiry or revoked access. Expired proposals retain their available title and preview for reference but cannot execute; request a fresh proposal.

An owner can explicitly allow automatic approval for limited draft-only text, color and layout edits. It is off by default and applies only before the app has any deployment record, including failed or preview deployments. Links, images, new components/content, records, backend changes and workflows are excluded. Automatic approval still saves a draft; it does not publish it.

Revoke a connection or choose Disconnect all AI clients to stop future access and reject pending proposals. Already approved workflows must be cancelled separately where possible. Sent messages and other completed external actions cannot be recalled.

26. Managed service, partners and credits

Chromoly offers Managed service for businesses and an invitation-only Partner tier for agencies and consultants. There is no public signup or self-service trial.

Managed service

Custom pricing: book a discovery call to agree the build and operating scope. Chromoly handles design, development, hosting and agreed maintenance. Your proposal defines integrations, included work, capacity and support. Existing contracts retain their agreed terms.

Partner

Custom pricing: book a partner call to agree hosting, delivery and support. Partners can build and publish any number of apps; each active published app incurs hosting charges. Each app includes up to 100 user accounts, 10 GB of uploaded files and 100 GB of outbound traffic per calendar month. These are seats and resource allowances, not a simultaneous-user guarantee. Extra usage is agreed separately. The partner manages client delivery and first-line support; Chromoly provides the platform and agreed technical support.

Partner workspace

After accepting your partner invitation, log in and open Partner workspace in the dashboard sidebar. Create a customer group, assign your existing apps, and open each app’s overview or Health & status. Only your own apps and groups are shown. You can rename or remove a group; removing it leaves the apps and their publication unchanged.

The workspace shows customer groups, saved apps, published apps and a base monthly hosting estimate. The estimate uses the platform’s standard rate and current published-app count. Your agreement determines your actual price; the estimate is not an invoice, a prorated bill or historical usage. Credits, VAT, extra usage and contract adjustments are separate. Health reflects recorded checks; “not checked” does not mean an app is healthy. Groups organise apps and do not grant customer access. Invite members and reviewers separately.

Welcome credits and additional purchases

Eligible new partners receive 5,000 credits once, after accepting the invitation, verifying their account and accepting the current terms. This is not a monthly grant. Already granted credits remain unchanged.

Open Credits → Buy credits: 10,000 credits cost €299, 25,000 cost €749, and 50,000 cost €1,499, before applicable tax. Stripe Checkout takes payment; credits arrive after payment confirmation. Purchases are one-time, without automatic refill.

Review the fixed quote before a build or edit. Model choice, app size and complexity affect the price. A 0.00-credit message does not make future work free. Supported in-app AI, agents and AI automation steps use credits or a configured BYOK connection. With BYOK, the provider charges you directly; builds, edits, hosting and other services remain separate. Runtime spending controls still apply.

27. Hosting and maintenance

Hosting and maintenance are delivered according to your managed-service or partner agreement. Confirm who manages domains, renewals, credentials, integration accounts, monitoring, backups and incident response before launch.

A successful build, an export button or a health screen does not by itself establish scheduled backups, tested recovery or an uptime SLA. Your agreement and the delivery team's operational checks define those commitments.

28. Data and access

Chromoly plans to migrate the primary platform database, authentication, file storage and realtime services to self-hosted Supabase on UpCloud in Stockholm, Sweden. The migration is not yet complete. Current services continue to use Supabase Cloud, Vercel and Hetzner as applicable until migration and verification are complete.

Self-hosted infrastructure

In the planned setup, Chromoly will operate the Supabase software and manage its configuration, access controls, updates and recovery arrangements. UpCloud will supply the underlying infrastructure. This is self-hosted Supabase software, rather than the Supabase Cloud managed service.

The primary hosting location does not determine where AI providers, email, payments, support, backups or customer-connected services process data. Their scope, locations and applicable safeguards are disclosed separately. EU hosting is not a guarantee of immunity from foreign legal requests or automatic compliance with every regulatory requirement.

Current infrastructure includes Supabase Cloud in Ireland, Vercel hosting with Dublin server functions and global edge delivery, and Hetzner Dev services in Helsinki. Providers will remain listed while they process data, including retained backups. Contact hello@chromoly.io for the arrangements applicable to your environment.

Use the processing settings for your app and review the Privacy Policy, DPA and subprocessor list. EU database hosting does not determine where a connected service processes data. Zero-data-retention coverage is also separate from processing location.

Keep customer data out of public assets and support screenshots. Use app-scoped roles and grant external clients only what they need. Revoking access prevents future authorised use; it does not erase copies already shared with an external service.

29. Exports, repository access and handover

The owner can request a ZIP archive from Publication & ownership. It includes supported app-specific models, generated backend source, records and stored files, with a manifest describing exclusions/redactions. Credentials are excluded; reconnect services during migration. External services and remote URLs are references, not copied backups.

Download links expire after five minutes and stored export files after one day. Large apps beyond the online export limit require an assisted export. For a final handover, coordinate a pause in edits/uploads and verify the manifest. The shared Chromoly runtime is not included, so the archive is not a standalone app guaranteed to run elsewhere.

The owner can separately invite a customer's GitHub username with read-only access to an eligible app repository in the configured organisation. Personal repositories do not support this read-only invitation flow. Reading the repository does not grant editing or ownership of Chromoly's platform.

Changes made outside Chromoly, including to downloaded or exported code, are outside managed support for those changes and any failures they cause, as set out in your agreement. Direct repository changes can be overwritten at the next publication. Use Chromoly's change flow for maintained updates and agree handover details before cancellation.

30. Troubleshooting and support

Use Profile → Support where available, or email hello@chromoly.io. Include the app name/link, time and time zone, expected result, error text and a screenshot without private records. Never send passwords, API keys or invitation tokens.

For managed support, our initial response target is within 24 hours. This is a response target, not a resolution deadline or a promise of 24/7 incident coverage. Your agreement defines coverage, escalation and any service commitments.

31. Language and regional settings

Generated interfaces support English and Swedish. Specify the language in the brief. Platform guidance is in English; some review screens use Swedish labels. Choose reporting time zone and currency explicitly rather than inferring them from language.

32. Larger builds and recovery

The builder runs supported structure, code and behavior checks and can attempt targeted repairs. A passed check is not proof that every API, integration or business rule works. If repair attempts are exhausted, keep the build reference and contact support; repeating the unchanged build does not reset its repair limit.

Larger structured builds may run in saved phases. Provider limits, validation or capacity can queue, pause or stop work. Follow the displayed recovery action and retain the build reference. Do not create repeated requests when an external action may already have completed.

Before launch, test representative records, member/admin access, approval and publication, domain/login behavior, connected services, scheduled work and recovery. Agree capacity and support for your real workload.

33. Key terms