App
JAMARQ Align
Google Business Profile work across many clients and locations, plus a measure of whether AI assistants name a business.
Began 2026-05-03 as tenra Align; renamed JAMARQ Align 2026-09-14; Tally folded in 2026-10-01; Tauri since 2026-08-24.
Why it was built
Looking after Google Business Profile for several clients means reviews, profile quality, sync problems, performance and client reports, repeated for every location. That work needs one place where all of it can be reviewed together.
Align is one controlled place for that work. Google's capability and approval limits stay visible on screen, sign-in tokens stay on the backend, and any write to Google stays behind a gate.
The Visibility section answers a newer question: do AI assistants name this business when someone asks? It records the answer as a measured rate with the evidence behind it, rather than a guess.
At a glance
- Began
- 2026-05-03
- Status
- In use
- Runs as
- Tauri desktop app over a local API and web interface
- Folded in
- Tally, Proxy's shaping engine
What it does today
Built and working
One review inbox
Reviews from every location in one list, each with a work status and a reply draft.
Location health and performance
A board showing which profiles need attention, and a triage view for performance across locations.
Replies that pass review
Each reply is shaped inside Align, then reviewed through Guardrail before it is posted by hand.
Client-ready reports
Reports written to hand to the client, covering reviews, profile health and performance.
Dry runs before writes
A write-readiness dry run shows the exact payload that would go to Google, without calling Google.
Visibility
A rate for how often assistants name a business, with the answer behind every data point kept as evidence.
How it came to be
The development cycle
152 commits and 63 merged pull requests, as of 2026-10-05. Work went straight to the main branch until August 2026, when every change started going through a pull request.
2026-05-03
Scaffold and a macOS launcher, on Electron.
2026-05-05
Google provider readiness and the outline of Google sign-in.
2026-05-29
Read-only import from Google.
2026-06-29 to 06-30
Workspace sync, multi-location boards, a daily queue, a reply library, reports, write-readiness dry runs, a SQLite store, encrypted backups and an audit evidence chain.
2026-07-11 to 07-20
Handling for expired tokens, and an export that proves each workflow.
2026-08-23
Import of visibility briefs from Tally.
2026-08-24
Moved from Electron to Tauri. The app went from about 269 MB to 122 MB.
2026-08-24 to 08-30
Plain-language pass across the interface.
2026-09-14
Renamed JAMARQ Align, with a new Google Cloud project of its own.
2026-10-01 to 10-02
Tally became the Visibility section, replies started being shaped in the app, and the old naming mechanisms were retired.
What was folded in
2 apps became part of this one
Earlier tools that did one piece of this job on their own. Their work moved here and their repositories were archived.
Tally
2026-08-16 to 2026-10-01
Tally measured whether assistants name a business, across 49 commits as Tally by Tenra. It went desktop on 2026-08-22 and moved to Tauri on 2026-08-23, as the reference build for moving the apps to Tauri. It became the Visibility section.
Proxy's shaping engine
Copied in 2026-10-02
Proxy itself was folded into Assembly. Its shaping engine was copied into Align so replies are shaped in the app, and the copy is kept identical to Assembly's by a drift check.
Where it stands
Real, and not yet
- •Google reads through the earlier approved Google Cloud project.
- •The review inbox, location health, performance triage, reports and write dry runs.
- •The Visibility section is built.
Not built, or switched off
- Writes to Google are off by design. Replies are posted by hand after review.
- Business Profile API access for the new Google Cloud project is pending. Until Google approves it the quota is zero.
- Visibility has not made its first real run.
- A pass to make the interface both simpler and deeper has not started.
How it is built
Under the hood
The pieces
- Shell
- Tauri desktop app over a local API and web interface
- Stack
- Express, React, Vite, SQLite, in one pnpm workspace
- Data
- SQLite in the user's config folder on the machine it runs on
- Tokens
- Kept on the backend, never in the browser
- Never
- Writes to Google. Every reply is posted by a person
Works with
- JAMARQ Guardrail
The approval inbox the other apps send their risky actions to.
- JAMARQ Assembly
The workbench where posts and documents are drafted, shaped, reviewed and approved.
The service behind this
Need a tool like this for your own work?
Describe the job it would do and what you use today. You will hear back within one business day.