Automatisch, Apple's container tool and Anime.js are three open source projects. They suit developers who need workflow automation, Linux containers on a Mac or JavaScript animation. This June 2025 roundup introduces each one. The sections added in November 2026 answer what developers ask next. They cover how to install each project, how it works, which license covers it and which version is current.
Automatisch: Your Self-Hosted Automation Solution#
https://github.com/automatisch/automatisch
Automatisch is an open-source alternative to Zapier that puts you back in control of your data and workflows. This business automation tool lets you connect services like Twitter, Slack, and others without any programming knowledge, but crucially runs on your own servers instead of the cloud. Perfect for GDPR-compliant businesses that can't risk exposing sensitive data to third parties, Automatisch offers both community (AGPL-3.0) and enterprise editions with Docker Compose deployment and zero vendor lock-in, making it an ideal solution for organizations seeking workflow automation without the subscription fees or privacy concerns of cloud alternatives.
What is Automatisch, and why self-host it on your own servers?#
Automatisch is a business automation tool that, in its README's words, lets you "connect different services like Twitter, Slack, and more to automate your business processes." The reason to self-host, per the README, is that it allows you to "store your data on your own servers," which it calls "essential for businesses that handle sensitive user information and cannot risk sharing it with external cloud services."
The roundup's summary describes that as how Automatisch "puts you back in control of your data and workflows." The README adds that self-hosting is "especially relevant for industries such as healthcare and finance, as well as for European companies that must adhere to the General Data Protection Regulation (GDPR)." The README heading calls Automatisch an "Open Source Zapier Alternative."
The README also compares Automatisch with "other existing solutions in the market, like Zapier and Integromat." Its last advantage is "No vendor lock-in." If Automatisch stops helping, the README says, "you can switch to any other provider." The home page says Automatisch "enables users to avoid the risk of becoming dependent on a single vendor or technology." It adds that vendor lock-in "can limit flexibility and increase costs."
How do you install Automatisch with Docker Compose?#
The README installs Automatisch in three steps: clone the repository, change into its folder and run docker compose up. The Installation docs then say to browse http://localhost:3000. That is the "Docker Compose deployment" in the roundup's summary of Automatisch.
# Clone the repository
git clone https://github.com/automatisch/automatisch.git
# Go to the repository folder
cd automatisch
# Start
docker compose upThe README clones over HTTPS. The Installation docs show the same steps but clone over SSH with [email protected]:automatisch/automatisch.git.
The README gives the sample login [email protected] with the password sample. It also says "Please do not forget to change your email and password from the settings page."
The repository's docker-compose.yml defines these services, read on November 18, 2026.
| Service | What the compose file sets |
|---|---|
| main | Publishes port 3000:3000 and waits for the postgres service to be healthy and the redis service to start |
| worker | Uses the same build as main, with the environment setting WORKER=true |
| postgres | Runs the image postgres:14.5 |
| redis | Runs the image redis:7.0.4 |
The Installation docs warn about two environment variables. ENCRYPTION_KEY and WEBHOOK_SECRET_KEY "are used to encrypt your credentials from third-party services and verify webhook requests." The docs add: "If you change them, your existing connections and flows will not continue to work."
To upgrade with Docker Compose, the docs say to run git pull origin main and then docker compose up --force-recreate --build.
For plain Docker, the Installation docs say: "Automatisch comes with two services which are main and worker." They "both use the same image and need to have the same environment variables except for the WORKER environment variable which is set to true for the worker service."
How do apps, connections, flows and steps work in Automatisch?#
A flow is a chain of steps that starts with a trigger and continues with actions. Each step uses an app through a connection that holds that service's credentials. In the roundup's summary, that is how Automatisch lets you "connect services like Twitter, Slack, and others without any programming knowledge."
The Key Concepts page covers "four main terms of Automatisch." Here are its own words for each one.
| Term | What the Key Concepts page says |
|---|---|
| App | "Apps are the third-party services you can use with Automatisch, like Twitter, Github and Slack." |
| Connection | "Connection is essentially the place where you pass the credentials of the specified service" |
| Flow | "It's a place to arrange the business workflow by connecting multiple steps." |
| Step | "Steps are the individual items in the flow." |
The same page gives the rule for order. "The first step of each flow should be the trigger step, and the following steps should be action steps." Its docs introduction says the software helps with your workflows "by integrating the different services you use."
The Create flow page builds an example that fetches new submissions from Typeform and sends them to a Slack channel. It says "Published flows will be executed automatically when the trigger event happens or at intervals of 15 minutes depending on the trigger type."
The Key Concepts page links a "complete list of available apps." The home page says "We integrate with the most widely used online services in the market," under the heading "An opportunity to use different integrations easily." It also says Automatisch "helps you to automate your business processes without coding." The Gnar Company's November 2026 post on AI workflow automation for operations teams covers when a no-code tool is enough and when a custom build makes sense. The post says: "A no-code tool is often enough for a simple, low-risk workflow between apps it already connects to. A custom build makes more sense when the work has to follow your own business rules, needs approvals and a record of every action, or has to write into an ERP the tool does not reach well."
Which license does Automatisch use, and what is its latest release?#
Automatisch Community Edition is "an open-source software with the AGPL-3.0 license," and Enterprise Edition is "a commercial offering with the Enterprise license." On November 18, 2026, the latest release was v0.15.0, published August 8, 2025. That is the split behind the "community (AGPL-3.0) and enterprise editions" in the roundup's summary. Under the heading "Join our open source community," the home page says: "We have an open source community where we encourage collaboration between different people and users."
The License page draws the line by file name: "All files that contain ".ee." in their name fall under the Enterprise license. All other files fall under the AGPL-3.0 license."
On the same date, the GitHub repository was not archived. The latest commit on its main branch was dated January 15, 2026. These are the five newest entries on the releases page.
| Release | Published on GitHub |
|---|---|
| v0.15.0 | August 8, 2025 |
| v0.14.0 | November 18, 2024 |
| v0.13.1 | August 2, 2024 |
| v0.13.0 | August 2, 2024 |
| v0.12.0 | May 28, 2024 |
Apple Container: Native Linux Containers on Apple Silicon#
https://github.com/apple/container
Apple has quietly released a developer tool that brings lightweight Linux containers to Mac through virtualization, optimized specifically for Apple silicon. Written entirely in Swift, the container tool creates OCI-compliant Linux containers as lightweight VMs, offering superior performance compared to cross-platform solutions like Docker Desktop while maintaining full compatibility with standard container registries. Though it requires macOS 26 Beta 1 for optimal functionality, this project showcases Apple's continued investment in native developer tooling and represents a compelling option for Mac-centric teams looking to integrate containerized workflows without compromising on performance.
What do you need to install and run Apple's container tool?#
You need a Mac with Apple silicon, which fits the "optimized specifically for Apple silicon" in the roundup's summary. The README, read on November 18, 2026, says container "is designed to run on macOS 26 or later." It adds: "We do not support older versions of macOS." You install the signed installer package from the GitHub release page, then start the system service with container system start.
The README's first run is container run --rm alpine echo hello. It pulls the alpine image, runs it in a Linux VM, prints hello and removes the container when it exits.
To upgrade, the README says to stop the existing tool with container system stop and then run /usr/local/bin/update-container.sh. GitHub lists the license as Apache-2.0. These are selected releases from the releases page, with dates in UTC, where 1.7.1 was the latest on November 18, 2026.
| Release | Published on GitHub |
|---|---|
| 0.1.0 | June 9, 2025 |
| 1.0.0 | June 9, 2026 |
| 1.6.0 | October 20, 2026 |
| 1.7.1 | November 6, 2026 |
How does container run Linux containers, and what are its limits?#
Apple's technical overview says that, using the open source Containerization package, container "runs a lightweight VM for each container that you create." The overview lists a memory limit: "Currently, memory pages freed to the Linux operating system by processes running in the container's VM are not relinquished to the host." It continues: "If you run many memory-intensive containers, you may need to occasionally restart them to reduce memory utilization." The typical way to run Linux containers on macOS, the overview says, is "to launch a Linux virtual machine (VM) that hosts all of your containers." The VM for each container is how it makes the "OCI-compliant Linux containers as lightweight VMs" in the roundup's summary.
The overview, read on its main branch on November 18, 2026, lists Security and Privacy among its properties. Security: "Each container has the isolation properties of a full VM." Privacy: "you mount only necessary data into each VM."
The overview names the macOS technologies that container and the Containerization package use.
| macOS technology | What it is used for, in the overview's words |
|---|---|
| Virtualization framework | "for managing Linux virtual machines and their attached devices" |
| vmnet framework | "for managing the virtual network to which the containers attach" |
| XPC | "for interprocess communication" |
| Launchd | "for service management" |
| Keychain services | "for access to registry credentials" |
| Unified logging system | "for application logging" |
On images, the README says the tool "consumes and produces OCI-compatible container images, so you can pull and run images from any standard container registry."
The README adds that parts of the tool marked experimental, for example the cluster subcommand, "may change and do not guarantee backward compatibility."
Anime.js: The Modern Animation Powerhouse#
Anime.js has evolved into a comprehensive JavaScript animation engine that surpasses typical browser limitations with a unified API for animating anything on the web. This versatile library offers a modular architecture where you can import only what you need, while packing features like SVG morphing, motion path following, scroll-triggered animations, draggable elements, and timeline orchestration with sophisticated easing functions. What makes it shine is the perfect balance between simplicity for beginners creating effects with minimal code and the depth needed for complex professional animations, all while maintaining excellent performance and a developer-friendly experience that competes with heavier weight graphic frameworks.
How do you install Anime.js and import only the modules you need?#
Install the animejs package with npm install animejs, then import functions by name, such as import { animate } from 'animejs';. The Module imports page says Anime.js "allows importing specific functionality from a subpath," either "by using a bundler like Vite or esbuild, or natively without a build step using importmap." It explains why: "When not using a bundler, or when tree shaking cannot be activated in a project, the entire library needs to be imported even when only using one module." It adds: "Each function can be imported directly from its subpath." The Installation page shows both steps. The roundup's summary says you can "import only what you need."
The Module imports page explains the result: "This approach ensures that only the code required for the specified functionality is loaded." These are some of the subpaths its list shows, read on November 18, 2026.
| Subpath | Function the docs import from it |
|---|---|
| animejs/ | animate |
| animejs/ | createTimer |
| animejs/ | createTimeline |
| animejs/ | createAnimatable |
| animejs/ | createDraggable |
| animejs/ | createScope |
| animejs/ | splitText |
| animejs/ | stagger and random |
The Installation page also gives a CommonJS line, const { animate } = require('animejs');, and CDN builds from esm.sh and JsDelivr.
What changed between Anime.js v3 and v4?#
Version 4 replaced the global anime object with the animate import, and the migration guide lists the changes. Version 4.0.0 was published on GitHub on April 3, 2025. The latest release on November 18, 2026 was v4.5.0, from June 22, 2026.
The README links the guide as its "V3 Migration guide." These are some of the renames it lists.
| Anime.js v3 | Anime.js v4 |
|---|---|
| targets parameter | first argument of animate |
| easing: 'easeOutQuad' | ease: 'outQuad' |
| direction: 'reverse' | reversed: true |
| direction: 'alternate' | alternate: true |
| anime. | createTimeline() |
| update, begin, complete | onUpdate, onBegin, onComplete |
The guide says the new default easing function name is "out(2)." It also says the loop parameter "now defines the number of times the animation repeats, instead of defining the actual number of iterations."
The README footer lists the "MIT License," and on November 18, 2026 npm lists 4.5.0 as the latest version, also under the MIT license.


