Plans and billing

Skyelight bills each organization for its plan and its seats. Reviewers don’t take a seat and are free on every plan.

Plans

Each paid plan has a base price that includes the owner’s seat, plus a price for each extra seat.

On Free, a coding agent connects to the Skyelight MCP to list your workspaces and projects and to publish review links with publish_review_link. Free hosts one prototype, with any number of versions. Reading and working feedback with an agent, and handing threads to an agent, are on Pro and above. See Requirements and Hosted prototypes.

A monthly bill is the base price plus the extra-seat price for each seat after the first. For example, 5 people on Team, billed yearly, cost $49 + 4 × $12 = $97 a month.

Seats

A paid seat is one person who holds an owner, admin or collaborator role in any of your organization’s workspaces. One person in five workspaces takes one seat. Reviewers never take a seat.

• Adding a seat is charged immediately, for the rest of the billing period. Before anyone confirms an invite or a role change, Skyelight says whether it adds a seat. If it does, the panel shows three lines: This seat (the extra-seat price), Charged today, for the rest of this period, and From your next invoice (your new total). Only the organization owner sees the exact prorated amount. Admins see the list price.
• An empty seat is free to fill. If you’ve paid for more seats than are in use, adding someone fills an empty seat, and the panel quotes $0.
• Seats don’t decrease automatically. When someone leaves or becomes a reviewer, their seat stays paid for. The next person you add fills it at no extra cost.
• Releasing seats. The organization owner clicks Release on the Billing page. The unused time becomes a credit on your next invoice, not a refund to the card. You can release seats down to the number in use, and never below one, because the base price covers the first seat.

Upgrading

The organization owner can buy Pro or Team, billed monthly or yearly, and pay by card or US bank account. You can buy extra seats at the same time, and Billing counts them as soon as the payment goes through. Card details go to Stripe and never reach Skyelight’s servers. A switch between paid plans takes effect immediately, and the difference is charged or credited at once. You can’t move from Team to Pro while the organization has more than one workspace.

If your bank needs to verify a payment, a plan change waits until you finish verifying. If you abandon the verification, the plan stays as it was. When a payment is waiting on you, the Billing page shows it under the plan:

• Complete payment finishes a verification your bank asked for.
• Pay invoice opens the invoice so you can pay it, for example after a card was declined.

Moving to Free

Moving to Free cancels the subscription at the end of the period you’ve paid for. Until then your paid plan keeps working, and the Keep button on the Billing page (for example, Keep Pro) cancels the move. To move to Free, the organization must already fit Free’s limits: one workspace and one paid seat. Reviewers don’t count. The Billing page lists the features you would lose.

If a payment fails

Stripe retries the payment, and your plan keeps working while it does. If the payment still fails, the organization moves to Free’s limits:

• Skyelight deletes nothing. Workspaces, projects, threads, screenshots and page context stay, and screenshots and page context keep your paid plan’s retention period.
• Slack, Linear and GitHub stop working, and coding agents get only what Free includes. They start again when you pay, without reconnecting.
• You can’t create more workspaces or projects than Free allows until you pay.

Stripe sends receipts, invoices and payment reminders to the organization owner’s email. The owner can also see invoices on the Billing page.

Auto-classifications on Free

Free includes 20 automatic classifications a month for the whole organization. Each one sets a thread’s type and writes its one-line summary. The month starts on the day of the month the organization was created, so an organization created on the 20th resets on the 20th. When the 20 are used, new threads still arrive, without a summary, until the next month starts.