Skip to content

Limits

You share files by pressing + in the message box of a mission dialogue. A shared file is kept with the mission, shown only to the mission’s members, served only as downloads and never opened in the console, and Cora can read it when it works on the mission. Shared files are not scanned for malware in this version (D0548, D0562). The rules are explained in files shared in the dialogue.

These are the seven types D0089 allows:

  • PDF
  • Word (.docx)
  • Plain text
  • Markdown
  • CSV
  • PNG
  • JPEG

The type is checked from the file’s first bytes on the server, not only from its name or what the browser says it is. A file that is not one of these types is refused.

Limit Value
Maximum file size 25 MB per file
Files per message 5

That is up to 5 files a message, each up to 25 MB. A file over the size limit, or a message with too many files, is refused before it is shared, with a message naming the limit (D0548).

  • Your browser sends the file straight to storage in the Sydney region through a single-use link that works for that one file only, for a few minutes.
  • The server then checks the file’s type and size and, if it passes, keeps it with the mission. It is available at once: it is not scanned for malware (D0562).
  • Only members of the mission can see the file or download it. Each download is a short-lived link that saves the file to your device; the file is never opened in the console, and images are not previewed.
  • The file is kept with the mission’s messages for as long as they are kept.

Cora can read a shared file named in a message while it works on that mission: the text of a document, or one image. It does not change the file. Reading a file counts toward the organisation’s spend cap (D0550).

Related: files shared in the dialogue and the mission dialogue.

Every value on this page is configuration, not code (D0011). The catalogue lives in packages/plans/plans.json, and the public pricing page, the console and the API all read it.

All prices are in US dollars. Every plan has every feature; plans differ only by AI usage, people, missions in the trial, and support (D0860).

Variable Meaning Value
currency The currency of every price. USD only
trial.days How long the free trial lasts. 14 days
trial.cardRequired Whether a card is taken before the trial starts. No
trial.usageUsd The AI usage the whole trial may use. Counted over the trial, not by month, and the organisation cannot raise it. A quarter of Standard’s monthly AI usage, in total
trial.members Members allowed in a trial. A 6th invite is refused. 5
trial.projects Active missions allowed in a trial. A 4th is refused. 3
trial.memberNoticeDays Members see the trial row in the account menu, and the dot on the account button, in the last this many days, or when paused. 3
tiers.standard Standard: the price a month, the AI usage a month, the members included, unlimited missions, and the price of each extra member. US$49 a month, the base amount of AI usage, 5 members, extra members US$9 a month each
tiers.pro Pro: the price a month, the AI usage a month, the members included, unlimited missions. US$199 a month, 5x Standard’s AI usage, 15 members
tiers.enterprise Enterprise: custom price and usage, set by a contract. No price in the file
yearlyMonthsFree A yearly plan costs twelve months less this many. 2, so ten times the monthly price
overageMarkupPercent Not used yet. Usage above what a plan includes is not billed: Cora pauses until the next month instead (D0666). The setting is kept for when such usage is billed, and nothing reads it today. 20, not applied

Paying by card (US-01M74YEN, D0660 to D0672)

Section titled “Paying by card (US-01M74YEN, D0660 to D0672)”
Variable Meaning Value
Stripe price cora_standard_month, cora_standard_year The Standard prices, found by lookup key. US$49 a month, US$490 a year
Stripe price cora_pro_month, cora_pro_year The Pro prices. US$199 a month, US$1,990 a year
Stripe price cora_extra_member_standard_month, cora_extra_member_standard_year One extra member on Standard: the quantity is the members past 5. US$9 a month, US$90 a year
PAST_DUE_GRACE_DAYS Days Cora keeps working after a payment first fails (@cora/domain/plans). 14
Included usage as the cap A paid plan’s monthly spend cap is its included AI usage; usage above it is not billed yet. Standard’s AI usage on Standard, 5x that on Pro
Secrets Manager core/stripe/secret-key, core/stripe/publishable-key The Stripe keys, made by hand, sandbox until live keys are chosen. Never shown or logged
Secrets Manager core/stripe/webhook-secret The webhook’s signing secret, made by the setup function. Never shown or logged
STRIPE_WEBHOOK_FUNCTION_NAME, STRIPE_SETUP_FUNCTION Production variables that switch on the deploy steps for the webhook code and the Stripe setup. Set after the first hand deploy

The prices are made in Stripe by the setup step from packages/plans, so changing a number in the file and deploying changes Stripe (a new price takes over the lookup key).

An organisation’s plan is a record (org_plans): the plan (trial, Standard, Pro, Enterprise or internal), its status (trialing, active, past due, canceled or paused), when the trial started and ends, the usage included, the credits the trial has used, the member and mission limits, and why a trial paused. An organisation made before the trial existed is on the internal plan, with no limits. Cora counts AI usage in credits on the server. The console and these docs show it only as a share of what the plan includes, never in dollars (BG-01M7QVN5, BG-01M7RGZC).