Work
What we build.
We'd rather show working software than promise it. This is our most complete case, and the one we use to prove the method.
Our own product
bb-sign: electronic signatures with verifiable evidence.
We built it end to end: a mobile-first signing ceremony, public document verification, a full audit trail and an API to plug it into your systems.
- API
- REST with an OpenAPI contract
- SDK
- Java and JavaScript
- Webhooks
- HMAC-signed
- Accessible
- WCAG AA in both themes
The challenge
The signer has no account, no training and nobody to ask: just a link and a document they need to trust. And a third party must be able to prove, long after, that the signature is authentic.
What we built
- A mobile-first signing ceremony, with the document visible before signing
- One-time passcode (OTP) verification with controlled resend
- Signing order for when signers must sign in sequence
- Public verification of the sealed document, without signing in
- A downloadable signed copy for every signer
- Signed webhooks to learn about every event without polling
- Interface in Spanish and English, with light and dark themes
How it is made
- Services
- Java microservices with Spring Boot
- Interface
- React and TypeScript
- Data
- PostgreSQL and S3-compatible storage
- Events
- RabbitMQ, event-driven choreography
- Identity
- Keycloak and OAuth 2.0 machine credentials
- Observability
- OpenTelemetry, Prometheus and Grafana
For developers
Your first envelope, in under 30 minutes.
Docs measured with real developers: if you have to ask, that's a bug in the docs.
curl -s -X POST "$BBSIGN_BASE_URL/api/v1/envelopes" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"title": "My first envelope",
"otpRequired": false,
"expiresAt": "2026-12-01T00:00:00Z",
"signers": [{"email": "someone@example.com", "name": "Someone", "signOrder": 1}]
}'
Facing a similar challenge?
If your operation depends on documents, approvals or systems that don't talk to each other, let's talk.
Book a conversation