The platform
The frame products are built in.
CoreFrame holds what every operational business application needs, so each product can concentrate on what makes it different.
How it fits together
Platform below, products above, a clear line between them.
Products depend on the platform; the platform never depends on a product. Marketing concepts such as brands, contacts and campaigns live in the Mail module, which keeps the platform reusable for whatever comes next.
Products
- CoreFrame MailAudiences, templates, campaigns, delivery
- Your next productSame foundations, its own domain
Platform
- Sign-in, roles and permissions
- Record scoping
- Audit trail
- Approvals
- Files and secrets
- Queues and scheduling
- API access and webhooks
- Import and export
Capabilities
What every product gets.
01Identity and access
- Invite-only users, no public sign-up
- Two-factor authentication, enforceable by policy
- Passkeys, passwordless or as a second factor
- Session overview with remote sign-out
- Roles with permissions declared by each module
- Record scoping carried into screens, jobs, exports and files
02Control and accountability
- An audit trail for important changes
- An approval inbox for actions that need a second pair of eyes
- A capability registry: every action behind a permission check and rate guardrails
- An operator view for queues, failures and anything stuck
03Data and modules
- Module definitions: entities, fields, tabs and actions, versioned and checksummed
- Definitions exported and imported between environments
- Data tables with server-side paging, sorting and filters
- Queued imports and exports with result reports
- Saved reports over validated query plans, never raw SQL
04Integration and operations
- API tokens for machine clients, with scopes and usage tracking
- Signed inbound webhooks with de-duplication
- Safe outbound HTTP with host allow-lists and private-network blocking
- Private file storage with signed, expiring links
- Vault-backed secret references
- Background queues and a scheduler that scale out
The workspace
Fast to get around.
Command palette
Jump anywhere or run an action with ⌘K / Ctrl+K.
Light and dark
Both themes, following the system preference.
Consistent everywhere
Every product shares the same navigation, tables and forms.
Principles
Choices made on purpose.
01One company, one instance
Each company runs its own application and database. Isolation comes from the deployment, not from a filter in a shared database.
02Turning on is not the same as allowing
Enabling a module for an instance and permitting a person to use it are separate decisions.
03People approve risky actions
Actions with external or irreversible effects can be routed through an approval step with a recorded decision.
04Platform changes must be reusable
The platform grows only when a capability has value beyond one product.
Assisted operations
Assistants that work inside the same rules.
Ask CoreFrame in plain language to find records, prepare reports or propose an action. Assistants work through the same permissions, audit trail and approval inbox as everyone else: they propose, a person decides.
- Every proposal is checked against permissions and validated query plans.
- Write actions wait in the approval inbox for a human decision.
- Everything an assistant does is recorded.
For technical evaluators
For technical evaluators
- Backend
- Laravel, PHP 8.5
- Frontend
- Vue 3, Inertia, Tailwind CSS
- Database
- MySQL 8.4, one database per company
- Workers
- Redis-backed queues, horizontally scalable
- Modules
- Self-registering, with their own routes, pages, migrations, permissions and schedules
- Quality
- Automated tests, contract tests and load tests in continuous integration
Running marketing email across several brands?
See CoreFrame Mail with your own workflow in mind: your brands, your lists, your integrations.
Request a demo