BrandPulse
Dynamic content management and secure storage bucket.
BrandPulse
Access
Launching our Q4 brand refresh
Assets
Optimising · storing to secure bucket
- 1
Roles that mean something
Admin, editor and viewer are enforced by the database. An editor can draft; only an admin can publish or delete.
- 2
Assets processed on upload
Images are resized and converted to modern formats, videos transcoded, everything stored in a private bucket with signed URLs.
- 3
Structured stories
Content is blocks with a schema, not a blob of HTML, so it renders correctly on the website, in email and in the app.
Marketing teams need to publish without a developer; the business needs to know who changed what and that nothing leaks. BrandPulse is a content system built to satisfy both.
Stories, pages and campaigns are edited in a structured editor, assets go through an upload pipeline that optimises and stores them securely, and every action is tied to a role and a log entry.
What BrandPulse does
Role-based admin controls
Per-organisation roles with granular permissions, enforced by row-level security. Access reviews export in one click.
Media upload pipeline
Direct-to-storage uploads with server-side processing: optimisation, thumbnails, metadata extraction and virus scanning.
Dynamic story editor
Block-based editing with live preview, scheduled publishing, version history and one-click rollback.
The stack, and why each piece is in it
Technology choices are decisions with reasons. These are ours.
- React
- A block editor is a deeply interactive component; React's model keeps that complexity manageable and testable.
- Supabase / Cloudflare Storage
- Private object storage with signed access, in the same platform as the database and auth. Fewer vendors, fewer credentials.
- PostgreSQL
- Structured content, version history and permissions in one transactional store.
- Tailwind CSS
- Admin interfaces have hundreds of small components; a token system keeps them coherent without bespoke CSS.
What changes per client, and what does not
The core is proven and stays fixed. Everything that makes it yours is configuration.
Fixed
- Database-enforced permission model
- Versioned content with rollback
- Signed-URL private storage
Configurable
- Content types and their block schemas
- Roles and approval workflow
- Storage provider and CDN
- Front-end targets: website, app, email
Talk to us about BrandPulse
Share the outcome you need and any constraints you are working within. You will get a straight answer on scope, timing and cost from the engineer who would do the work.