Services
A service has one responsibility, its own interface, its own scopes and its own meter. It shares authentication, authorisation, auditing and the wire conventions with the other seven. You enable them one at a time.
The rows below are deliberately uniform. Every service answers the same five questions in the same order, so two of them can be compared without reading two differently shaped stories.
In the order the platform lists them. Rates are indicative and come from the platform's example catalogue; yours are confirmed before a service is enabled.
Managed document storage scoped to an organisation. Storage class, metadata and retention are yours to set; the size ledger and the audit trail come with it.
Text extraction, classification and field extraction as an asynchronous job. Priced per page or per whole document, whichever suits the work.
Signature envelopes with a full status history, drawn or typed capture in your own page, and server-side validation of every submitted signature. What is recorded is the signer reference, the capture method, the timestamps, the status history and the validation result.
Generation from your templates, with the fields the rest of the platform already holds. The output is a stored object like any other.
Availability, appointments and bookings against the constraints you publish. The customer books in your page, on a token scoped to that booking.
Email and SMS sent on the organisation's behalf, with a delivery record per message. SMS is metered by segment, because that is how carriers charge.
Identity and document verification as a single check with a recorded outcome. Enabled by agreement, because the providers behind it require one.
Postcode and address search, priced per lookup. The cheapest place to fix bad data is before it is stored.
Browser capabilities are a closed list, and that is the security property rather than a limitation. A token that could carry an arbitrary scope would be a secret key with a shorter life: something your backend could be talked into minting for anything.
Each capability is minted by your backend for one resource, for a few minutes. The component reads its limits off the token, so page code cannot widen them.
| Capability | Service | What the page may do |
|---|---|---|
| storage.upload | Storage | Accept files from the person in front of you. |
| storage.download | Storage | Let them read one file back. |
| sign.capture | Sign | Draw or type a signature in your page. |
| sign.complete | Sign | Complete a signature request. |
| forms.complete | Sign | Fill in and submit a form. |
| calendar.book | Calendar | Choose and hold an appointment. |
| documents.view | Documents | View a generated document. |
Retention is a business decision, so the class is explicit per object rather than inferred from how often something has been read lately. Volume held over time is what is charged; uploads and downloads are counted and free.
Send us the shape of the work. We will name the services that cover it, the operations you would be billed for, and anything on your list that Proxy does not do.