Ocalt for

Ocalt for Business

Run the business on one account that everyone works inside. Give each person exactly what they should reach — the files, the databases, the machines, the sites — and nothing they should not. Work switches to the business with one action, so a script written by anyone runs in the same namespace, against the same data, billed to the same place. From a two-person shop to a company with depots in three provinces, the structure is the same and it does not grow a middleware layer as you add people.

One namespace, many people

A business is not a folder shared between accounts. It is a namespace, and a member acting for it works inside it directly — same files, same databases, same registered machines. Nothing is copied, synchronised or exported between people, because there is only ever one copy.

Permission is per person, and it is narrow

What someone may do and where they may do it are two separate grants. A bookkeeper can reach the databases and the mail without touching a machine; an engineer can reach the machines without seeing the ledger. Neither can reach the plan, the billing or the API key — those never leave the owner.

The bill is one bill

Members work on the business allowance rather than their own. Every query is attributed and logged, so what the business spends is a number you can read rather than a surprise at the end of the month.

It is still just scripts

There is no separate business product to learn. The same language that reads a file reads the ledger; the same verb that restarts a server sends the invoice. Adding people does not change what the platform is, only who may point it at what.

In practice

SELECT ROWS FROM DB "sales" TABLE "invoices" WHERE "paid" IS IDENTICAL TO "no" SET ?due
AFTER FOREACH ?due SET ?inv
OPEN
  DOC CREATE FROM STRING ["Reminder: invoice " & ?inv("number")] AS "pdf" SET ?pdf
  AFTER MAIL TO ?inv("email") SUBJECT "Invoice reminder" BODY "Attached." ATTACH ?pdf
CLOSE
AFTER NOTIFICATION "reminders sent"

Set the business up

  1. Create the business in your Ocalt account. It is yours whatever plan you are on.
  2. Add the people who work in it. Each member is granted what they may do — run scripts, files, databases, subdomains, machines, mail — and which products they may open while acting.
  3. Switch to acting as the business. Everything then runs in the business namespace: its files, its machines, its sites, its query allowance. Account settings, billing and the plan stay with the owner alone.
  4. Watch what it costs. Every charged query is listed at accounts.ocalt.com/qllogs with what ran and where it came from.
NEW DB "sales"
AFTER NEW TABLE "orders" IN DB "sales" COLUMNS ADD "ref" TYPE STRING AND ADD "status" TYPE STRING
AFTER INSERT INTO DB "sales" TABLE "orders" ROW "ref" AS "A-1001" AND "status" AS "open"
AFTER SELECT ROWS FROM DB "sales" TABLE "orders" WHERE "status" IS IDENTICAL TO "open" SET ?rows
AFTER COUNT ?rows SET ?n
AFTER EMIT ?n & " orders still open"

Every plan, including Free, carries the whole language. Open the console, read the documentation, or see what a plan costs.