Trust & Security
Trust starts with visible controls
Optimic's public trust story is built around governed execution, clear technical foundations, and visible product surfaces. This page is intentionally narrow: it only covers controls and systems that are backed by the repo and live product surfaces.
Technical foundations
The public codebase and docs show a straightforward stack behind the platform.
- Go and Fiber for backend services
- Asynq for background job execution
- PostgreSQL and Redis for core data infrastructure
- Clerk for authentication
- Stripe for billing
- Next.js for the customer-facing web experience
What this page is not claiming
This is not a placeholder for unpublished certifications, vague platform language, or security promises that cannot be inspected.
If a control, policy, or proof point is not visible in the repo or product surfaces, it is not asserted here.
Governed execution surfaces
The strongest trust signal in Optimic is not abstract security copy. It is the fact that execution is paired with review, certainty, recovery, and traceability.
Review Queue for actions that need a human decision
AI certainty signals visible in review and workflow surfaces
Permissions and spending limits in Safety controls
Checkpoint, rollback, and recovery surfaces for operational changes
Activity log and audit trail views for traceability
Emergency stop controls when execution needs to pause fast
Public trust surfaces
Trust improves when a visitor can inspect how the system works, not just read a slogan. These are the public surfaces that support that.
Methodology
How AI visibility work is approached and governed.
Governance
Review, approval, rollback, and auditability story.
Documentation
Public docs, API entry points, and implementation references.
Proof Structure
Case study and API/docs proof placeholders without invented evidence.
Status
Operational status page for public visibility.