DEV Community: Westpoint io

We Open-Sourced Mimik 5 Months Ago. Now It Has 4,000+ Users and 1,600 GitHub Stars.

Westpoint io — Wed, 14 Oct 2026 17:15:23 +0000

Five months ago, we released Mimik, a free, open-source browser extension for turning browser workflows into step-by-step guides.

We originally built it at Westpoint to solve a problem we kept running into: spending too much time documenting workflows, taking screenshots, and explaining the same processes over and over.

We figured other developers probably had the same frustration.

What we didn't know was how many people would find it useful.

A few numbers we're pretty proud of

Since releasing Mimik in May 2026, we've reached:

4,000+ users on Google Chrome
1,600+ GitHub stars
198 GitHub forks
A growing community using Mimik across Chrome, Firefox, and Edge

For a free tool developed by a small engineering team, that's been really encouraging to see.

We're especially happy about the GitHub interest. Knowing that developers are finding the project, exploring the source code, and forking it is a big part of why we wanted to open-source it in the first place.

A quick reminder of what Mimik does

If you haven't come across it yet, Mimik automatically turns what you do in your browser into a documented guide.

Start recording, perform your workflow, and stop. Mimik captures the actions and generates a guide with annotated screenshots.

You can edit the steps, add descriptions, replay the workflow, and export it to Markdown, PDF, HTML, DOCX, GIF, or video.

It's useful for documenting internal tools, preparing tutorials, onboarding teammates, and sharing instructions without manually creating every screenshot.

And importantly, Mimik is local-first.

Your guides stay in your browser. There's no account to create, no backend to store your documentation, and no subscription to pay for. Optional AI features use your own provider credentials.

We're keeping it free and open source

As Mimik grows, we want to keep the original idea intact.

No subscription tiers. No locking core features behind a paywall. No requirement to sign up just to document a browser workflow.

The entire project is available on GitHub under the MIT licence.

We believe useful developer tools should be accessible, and we're happy to contribute something back to the community.

We're also continuing to improve Mimik, and community feedback is an important part of deciding what to work on next.

Thanks to everyone who's tried it

If you've installed Mimik, starred the repository, opened an issue, or shared it with someone, thank you.

It's genuinely rewarding to see a small internal idea turn into something thousands of people are using.

If you're new to Mimik, give it a try the next time you need to document a browser workflow.

And if you have ideas for improving it, we'd love to hear them.

Links:

If you find it useful, consider giving the repository a ⭐ on GitHub. It really helps an open-source project like ours reach more developers.

What feature would make Mimik more useful in your daily workflow?

Built with ❤️ by the engineering team at Westpoint.

E-invoice compliance coming into force in 2026

Westpoint io — Mon, 18 May 2026 16:25:00 +0000

E-invoicing compliance is becoming a real challenge for ecommerce merchants across Europe 🇪🇺

For Shopify merchants, the order data is already there: customer details, products, VAT, totals, dates, and payment information.

But in some countries, that data now needs to be turned into structured, compliant invoice formats.

That is why we built Billoop 🧾

Billoop is a Shopify app that helps merchants generate compliant invoice files directly from Shopify order data, starting with France-ready Factur-X invoices.

What it helps with:

✅ Generate compliant invoice files from Shopify orders
✅ Reduce manual invoice work
✅ Prepare for changing EU e-invoicing rules
✅ Keep the workflow close to the Shopify order page
✅ Support country-specific formats, starting with France
✅ German-compliant invoices are on the way

We kept Billoop focused on one practical problem:

Shopify merchants should not need to fight with invoice compliance manually when the order data already exists.

Billoop turns that data into the invoice format they need.

You can check it out here 👇
Shopify app store
Website

Would love feedback from Shopify merchants, agencies, and anyone working with ecommerce invoicing or EU compliance

I built Mimik: an open-source Chrome extension that auto-captures browser workflows into step-by-step guides

Westpoint io — Fri, 15 May 2026 11:58:19 +0000

🤔 Why I built this

We run a software agency and kept writing the same "how to do X in our admin panel"
docs for clients. Loom is too long. Scribe puts your data on someone else's server.
Screenshots in Notion decay the day after you take them.

🎬 Demo

Click record, do the workflow, click stop. You get a clean guide with one step
per action and an annotated screenshot per step.

✨ Features

🎥 Auto-capture clicks, typing, and SPA navigation - one step per intent
🤖 Optional AI step descriptions (BYO OpenAI / Anthropic key)
🔒 Smart blur - regex presets for emails, phones, cards, JWTs
✏️ Edit, reorder, delete any step before exporting
📤 Export to HTML, PDF, or Markdown - all client-side
🎓 Guide Me replay walks teammates through your saved guide on the live page
🌐 Same codebase ships to Chrome, Firefox, and Edge

🛠️ Tech stack

Extension framework: WXT on top of Vite
UI: React 19, Tailwind CSS v4, shadcn/ui
Capture state: xstate machine in the background SW
Storage: Dexie over IndexedDB
Messaging: @webext-core/messaging
AI: Vercel AI SDK with @ai-sdk/openai and @ai-sdk/anthropic
Export: jsPDF + client-side HTML/Markdown
Manifest V3 across all three browsers

🔒 Why local-first matters

(One paragraph: handover docs often contain credentials, internal URLs, customer
data. They shouldn't end up on a SaaS server. Mimik stores everything in IndexedDB
on your machine. AI calls are optional and go directly from your browser to the
provider with your own key.)

🗺️ Roadmap

Translation polish (good-first-issue tickets open for ES, pt-BR, FR native speakers)
Better Guide Me matching across DOM mutations
Notion / Confluence / static-site export

⭐ Try it

Install: [Chrome] · [Firefox] · [Edge]
Source: github.com/westpoint-io/mimik (MIT)
Website: Mimik
Website creators: WestPoint

If this is useful, a GitHub star goes a long way.

OpenClaw vs. Amazon Quick Suite

Westpoint io — Tue, 31 Mar 2026 12:55:26 +0000

Executive Summary

In early 2026, OpenClaw became one of the fastest-growing open-source projects on GitHub, passing
200,000 stars in under three months.

Built by Austrian developer Peter Steinberger, it introduced a much more operational model for AI:
agents that do not just respond, but autonomously execute multi-step tasks across real systems.

That adoption wave confirmed a major shift in buyer and developer interest:

Organizations increasingly want AI that acts, not just AI that advises.

At the same time, OpenClaw's rise also exposed a second reality. Once AI agents move from chat
interfaces into real execution, the hard problems are no longer only about model quality. They are
about security, governance, identity, auditability, and trust boundaries.

AWS is approaching the same direction from the opposite side.

Amazon Quick Suite, evolved from QuickSight, pushes toward agentic workspaces and business
automation, but does so inside a more structured enterprise control model.

The result is a useful contrast: OpenClaw proved demand, while Amazon Quick Suite represents the
kind of operating envelope enterprises are more likely to accept in production.

OpenClaw: The Agent That Went Viral

Architecture and core capabilities

OpenClaw is a locally hosted Node.js gateway that connects large language models to external
systems through a plugin architecture built around skills.

Its appeal was straightforward:

multi-step task execution
messaging-first interaction through tools such as Slack, Discord, and WhatsApp
scheduled automation through cron jobs
a large and rapidly growing ecosystem of community-contributed skills

This combination made OpenClaw feel less like a chatbot and more like an operator.

Adoption trajectory

The project's growth curve was unusually steep:

launched as Clawdbot in November 2025
renamed to OpenClaw in January 2026
passed 100,000 stars in February 2026
moved beyond 200,000 stars shortly after

Whether or not every growth claim remains stable over time, the broader signal was clear:
OpenClaw captured attention faster than most infrastructure or AI tooling projects in recent
memory.

The security reality

As adoption accelerated, security concerns surfaced just as quickly.

The reported issues around OpenClaw included:

hundreds of vulnerabilities, including critical findings
a remote code execution exploit
exposed API keys
malicious or unverified skills
prompt injection and memory poisoning scenarios

The point is not that open-source agent systems are inherently unsafe. The problem is that once an
agent can authenticate, call tools, access memory, and trigger actions, the blast radius expands
dramatically.

OpenClaw made that risk visible in public.

The enterprise identity gap

Traditional enterprise systems assume a mostly human-centered model of action:

Enterprise model	Agent reality
Users initiate actions	Agents may act autonomously
Permissions are scoped to people or roles	Permissions can be inherited by software agents
Audit logs often explain who did what	Intent can become harder to trace
Supply chains are formally reviewed	Community plugins may be unverified
Identity usually maps to humans or services	Agent identity can scale quickly and opaquely

This is where many agent platforms start to break down in enterprise settings. Execution is easy to
demo. Trust boundaries are much harder to operationalize.

Amazon Quick Suite: The Enterprise Answer

From QuickSight to Quick Suite

Amazon Quick Suite extends QuickSight into a broader agentic workspace that combines analytics,
automation, collaboration, and AI-assisted task execution.

In practical terms, it signals that AWS sees the future of business intelligence as more than
dashboards. The platform is moving toward systems that can research, automate, coordinate, and
assist inside controlled enterprise environments.

Core components

The suite is framed around several capabilities:

Quick Research for structured report generation
Quick Flows for workflow creation from natural language
Quick Automate for multi-agent orchestration with approvals
QuickSight for analytics and dashboards
Quick Spaces for team workspaces
Quick Chat Agents for configurable assistants

The underlying idea is similar to OpenClaw's vision: reduce the gap between intent and execution.
The delivery model is different.

Enterprise integration

Quick Suite is designed around managed integrations rather than a wide-open plugin marketplace.

Examples include connectors for:

Salesforce
ServiceNow
Slack
Gmail
Exchange
S3

That distinction matters.

OpenClaw scales through community skills
Quick Suite scales through AWS-managed integrations

The first model grows faster. The second model is easier to defend in enterprise environments.

Governance and compliance

Quick Suite is much more explicitly positioned around enterprise controls.

That includes alignment with frameworks and capabilities such as:

SOC
HIPAA
ISO 27001
ISO 27018
ISO 9001
GDPR
FedRAMP
role-based access control
audit logging
human-in-the-loop workflows

For enterprise buyers, these controls are not secondary product details. They are often the actual
buying criteria.

Feature Comparison

Capability	OpenClaw	Amazon Quick Suite
Automation	Community skills and cron-based execution	Structured workflow automation
Integration model	Community-contributed skills	Managed connectors
Research workflows	Depends heavily on model and prompt setup	Built-in research components
Knowledge model	Local or agent-managed memory	Shared and controlled spaces
Visualization	Limited	Full BI and dashboarding
Identity integration	Weak or inconsistent	IAM-aligned enterprise model
Auditability	Limited	Full logging and traceability
Approval controls	Minimal by default	Built-in approval flows
Security posture	High operational risk	Enterprise-oriented controls
Governance model	Open and unstable	AWS-backed and structured

Same Vision, Different Starting Points

What OpenClaw proved

OpenClaw proved several things very quickly:

demand for autonomous agents is real
messaging-first user experience drives adoption
open ecosystems can scale at extraordinary speed

It made the future feel immediate.

What OpenClaw cannot reliably deliver

For enterprise use, however, OpenClaw also highlighted what is still missing:

robust access control
durable auditability
compliance alignment
formal governance

That does not make it unimportant. It makes it a market signal rather than a production template.

OpenClaw is best understood as proof of demand, not proof of enterprise readiness.

Where Quick Suite wins

Amazon Quick Suite aims at much of the same destination:

autonomous execution
cross-system orchestration
persistent context

But it starts from the constraints enterprises already care about:

security
compliance
identity control
governance

That gives AWS a more credible path into production environments where risk, approvals, and audit
trails are part of the workflow rather than an afterthought.

The trade-offs

That does not mean Quick Suite is automatically the better answer in every setting.

It comes with trade-offs of its own:

AWS ecosystem lock-in
a narrower extension model than open-source ecosystems
subscription and platform cost considerations
the maturity risks that come with newly evolving product categories

The difference is that these are enterprise trade-offs, not existential trust-boundary gaps.

Conclusion

OpenClaw proved that the market is ready for AI agents that can act.

It also made visible how fragile open agent systems become when they move into real execution
without strong identity, control, and governance models.

Amazon Quick Suite represents a more enterprise-safe version of the same broader future.

The central question is no longer whether AI agents will operate across enterprise systems.

It is this:

Will they operate inside governance, or outside it?

Sources

Cleaning Node.js Build Artifacts with a CLI Tool

Westpoint io — Wed, 04 Mar 2026 12:31:30 +0000

Modern JavaScript and TypeScript projects generate a lot of build artifacts.

Directories such as:

node_modules
.next
dist
.cache
coverage
.turbo

appear across almost every project. When you work across many repositories these folders accumulate quickly and can easily consume tens of gigabytes of disk space.

Cleaning them manually is tedious.

So we built a small CLI tool called Dustoff.

What Dustoff Does

Dustoff scans your filesystem for common JavaScript and TypeScript build artifacts and allows you to browse and remove them interactively.

Instead of manually searching for folders, you get a terminal interface that lets you quickly identify and clean up unused build outputs.

Demo

Features

Dustoff includes:

scanning for common build artifact directories
sorting artifacts by size, path, or age
searching and filtering results
grouping artifacts by directory
keyboard navigation for selecting multiple items
safe deletion with confirmation

The goal was to create something simple that removes friction from a common developer problem.

Running Dustoff

You can run it instantly using:

npx dustoff

Or install it globally:

npm install -g dustoff

Open Source

Dustoff is open source and available on GitHub:

https://github.com/westpoint-io/dustoff

Also, here is the website:

westpoint-io.github.io

We originally built it as an internal utility while working across multiple JavaScript projects and decided to share it publicly once it proved useful.

If you run into similar cleanup issues across projects, curious to hear your feedback.

Built with love by Westpoint