Anyflow

Notes compiled from publicly available sources. Last updated: 2026-10-11. Every figure is linked to the source it came from and dated. Verify against primary sources before relying on them.

TL;DR

Anyflow (Anyflow株式会社, corporate number 1011001109588) is a Tokyo company whose main product, Anyflow Embed, is an embedded iPaaS (組み込み型iPaaS): SaaS vendors use its no-code editor, connectors and JavaScript SDK to ship integrations with other SaaS products inside their own product. It also sells Anyflow Automation, described on its product page as a "Headless iPaaS" for connecting a SaaS vendor's product with enterprise core systems (homepage; Undated; accessed 2026-10-11). The company dates its founding to 2016-02-12; the legal entity started as Revode株式会社, became 株式会社ピケ in 2017 and Anyflow株式会社 in 2019 (国税庁 法人番号公表サイト; record as of 2026-10-11). Since 2024-12-10 it has been a wholly owned subsidiary of アスエネ株式会社 (Asuene), a CO2-accounting SaaS company (Asuene release, Anyflow release; both 2024-12-10).

• Funding before the acquisition: a 2,000万円 seed round from Coral Capital (2019-09-24), a 約2.2億円 pre-Series A led by Global Brain and Globis Capital Partners (2020-01-08), and a capital and business alliance with Smaregi (2022-12-08, amount not disclosed). Asuene's acquisition release puts Anyflow's cumulative funding at "累計約3.4億円"; the purchase price was not disclosed (Asuene, 2024-12-10).
• Scale disclosed by the company: 247 integrations released by customers on Embed in its first year and more than 24 million cumulative executions (2024-07-16); "200種以上" connectable cloud services (2026-05-28). A 2025-06-11 release cites a Deloitte Tohmatsu MIC report naming Embed No.1 by share among "IT・Web向けSaaS開発連携型ツール" (2025-06-11).
• Headcount: "30名(業務委託含む)" (HERP posting, posted 2025-12-22; accessed 2026-10-11). Other company-published figures range from about 20 to "30名強" (see Notes).
• Engineering, per job postings: Embed is built in Python (FastAPI, Django ORM, Celery) with a TypeScript/React frontend, MySQL (Cloud SQL) and Redis, on GCP/GKE with Terraform and ArgoCD; the Automation team writes customer workflows in TypeScript (Deno, Node.js) on Cloud Run. The security policy states all production systems run on Google Cloud in Japan (security policy; Undated; accessed 2026-10-11). Postings are in Japanese and no English working-language statement was found; work is remote-first with a 10:30–17:30 flex core time (careers page; Undated; accessed 2026-10-11).

Basic

Identity and legal entities

The company's own notice dates the change to Anyflow株式会社 to 2019-01-17 (2019-01-17); the register records 2019-01-30 (see Notes).

Programs and awards (company-announced unless noted): finalist at the IVS 2019 Summer Launchpad, first overall at Incubate Camp 12th, winner of the B Dash Camp 2019 Fall Pitch Arena (pre-Series A release, PR TIMES, 2019-11-05); 優秀賞 at the 8th FUJITSU ACCELERATOR pitch contest (2020-02-10); EY Innovative Startup 2020 (PR TIMES, 2020-02-28); the original Anyflow product registered as an IT tool under the METI IT導入補助金2020 (PR TIMES, 2020-08-06); CEO named to Forbes 30 Under 30 Asia 2022, Enterprise Technology (2022-05-26). The careers page links elevator pitches at Startup Aquarium 2023 and 2024 (careers page).

Market context as stated by the company

• The Embed page cites SaaStr Annual 2021 for the claim that 30% of users considering a SaaS purchase require integration with other SaaS, and states that an in-house integration typically takes 3–6 months (Embed page; Undated; accessed 2026-10-11).
• A company survey of 111 B2B SaaS buyers (internet survey via IDEATECH's リサピー, fielded 2026-05-18 to 05-19) reports that 75.7% had excluded a SaaS for insufficient API integration before comparing features or price, and 63.1% had chosen a different service because of missing integrations (2026-07-14). The release headline uses a different figure (see Notes).
• Asuene's acquisition release frames the deal around Scope 1–3 disclosure under SSBJ standards and the effort of collecting activity data from ERP and SaaS systems (Asuene, 2024-12-10).

Product

What it is and its feature areas

Anyflow Embed — "SaaS事業者向けの組み込み型iPaaS" that lets a vendor deliver integrations with other systems "最短1週間" (homepage). Generally available since 2023-07-13 (2023-07-13); BRIDGE reported it had been in development for about two years and offered in stealth before then (BRIDGE, 2023-07-13). The documentation at docs-embed.anyflow.jp (149 pages in its sitemap, accessed 2026-10-11) is organized as:

Dated feature releases include "My Event" for vendors without a public API (2024-01-16), "リクエスト&レスポンス" for two-way exchange without a public API (2024-08-20), "コードアクション" for running code in a chosen language and version inside no-code flows (2025-04-17), and an "AI エージェント / RAG向けデータ自動連携サービス" that syncs customer data from Google Drive, Box, SharePoint, Gmail, Slack and others into a vector database (2026-05-28). The release notes list smaller changes through 2026-03-18.

Anyflow Automation — the product page describes it as "SaaS事業者向けのHeadless iPaaS" that integrates enterprise customers' existing systems with the vendor's SaaS, using APIs where available and CSV or database connections otherwise, with "100以上" connectors and fully managed infrastructure (Automation page; Undated; accessed 2026-10-11). Job postings describe delivery as customer projects: a workflow-building team writes each integration in TypeScript, generally waterfall, with enterprise projects under 10 person-months (workflow-builder posting, PM lead posting).

Other offerings. A 2026-03-31 notice ended four Smaregi-related integration apps on 2026-04-30 and named "Anyflow Connect" as their successor, at partly changed prices (2026-03-31); no product page for Anyflow Connect was found. The technical customer success posting refers to "Anyflow Embedカスタムメイド版" deployed for specific customers (posting).

Commercialization

No public price list exists for Embed or Automation; both product pages route to a demo or consultation form. The terms of use (enacted 2019-11-29, last amended 2022-07-20) define the fee components as an onboarding fee, a fixed monthly fee, a usage-based monthly fee, option fees and other fees, each set in the order form, invoiced and paid by bank transfer; fees for the full contract term other than usage fees are paid in one lump sum by the end of the month after service starts. The Embed page says building, designing, testing and deploying an integration can be done by the customer or delegated to Anyflow (Embed page). Earlier products published prices: Anybot "月額7万円から" during its beta (2018-10-24) and the original Anyflow "月額3万円から" (2020-08-06).

Reported scale over time

Announced customers and partners

Stated plans

• Code solutions: deployment, execution logs in the admin console and more supported apps before a formal release (2026-07-28).
• Group integration: use Asuene's sales base to expand Embed's sales network and apply Anyflow's integration technology to CO2 data collection (2024-12-10).
• Enterprise: an Enterprise BizDev posting describes the SMB business as growing and seeks a hire to roll solutions out to enterprise customers, naming regional banks (地銀) as example customers (posting, posted 2026-07-23).

Founder

坂本 蓮 (Ren Sakamoto) — 代表取締役CEO (company page).

• Started programming in junior high school (Wantedly posting, 2024-05-11, closed).
• In his fourth year at university, selected for KDDI's accelerator KDDI ∞ Labo; founded the company in February just before graduating because the program required one (Founder interview, 2019-06-17). BRIDGE reports that he earlier built AppMotor, a bug-fixing support platform for programmers, selected for ∞ Labo's 9th batch (BRIDGE, 2019-09-24).
• After graduating, joined CyberAgent, where he maintained Ameba infrastructure (Founder interview); a later posting describes the role as server-side engineer (Wantedly).
• Says he built about 20 products, including the lunch app "Dish", and that Anyflow started as an RPA product before pivoting to iPaaS (Founder interview). As CEO of 株式会社ピケ he announced the cloud RPA Anybot on 2018-10-24 (PR TIMES).
• Named to Forbes 30 Under 30 Asia 2022, Enterprise Technology (2022-05-26); listed inventor on JP7645548B2 (Google Patents).

Co-founders. BRIDGE named 中西 奎太 as co-founder in 2019 (BRIDGE, 2019-09-24); he is not listed on the current company page. The CEO interview says there are three founders, all engineers (Founder interview); the third founder is not named in any source reviewed.

Selected leadership

大久保 陽平 (Yohei Okubo) — 取締役CTO. Joined in January 2021, first as a contractor, working on the Celery-based workflow engine, SaaS connectors, CI automation, log monitoring and Kubernetes operations; about a year later the CEO and the previous CTO asked him to take the CTO role, and the previous CTO continued as an engineer on Embed. Earlier: ad-operations tooling at a large web advertising agency as a new graduate, then freelance tech lead, SRE and data engineering work (Green, accessed 2026-10-11). Listed inventor on JP7645548B2.

阿部 遼介 — 執行役員COO (company page). The Enterprise BizDev role reports directly to the COO (posting). No career background was found.

須永 智成 — Anyflow Embed 事業責任者・プロダクトオーナー; joined in 2023 after a financial group (smartphone-app PM) and the interactive-video startup MIL (2026-06-29).

A closed 2024 Wantedly posting also listed 松田 光希 (CFO, formerly IPO lead at a listed company) and 藤本 遼平 (marketing, ex-DeNA and Wantedly) (Wantedly, 2024-05-11); neither appears on the current company page. The careers FAQ gives the organization mix as engineers and designers 55%, CS/CRE and sales 40%, back office 5% (careers page).

Funding

Coral Capital invested in the seed round and again in the pre-Series A. The pre-Series A release stated the funds would go to product development and speed, and that the company planned to become a platform integrating and managing domestic and overseas SaaS (2020-01-08). The Smaregi alliance was announced together with Smaregi's use of Embed for POS–EC integrations, and the Yayoi alliance seven months later; Embed reached GA between them, on 2023-07-13. Neither the gap between 約2.6億円 (2020) and 約3.4億円 (2024) nor the Smaregi amount is broken down in any reviewed source.

Engineering

Technology stack and platforms

Confirmed by documentation or public assets

• Hosting: Google Cloud in Japan for all production systems and databases (security policy). The public status page tracks GKE, Cloud SQL and Stackdriver as components, plus Netlify (origin servers and edge network) (accessed 2026-10-11).
• SDK: @anyflowinc/embed-sdk, a JavaScript/TypeScript SDK on npm — first published 2023-05-19, v0.16.0 on 2026-03-18; its dev dependencies include TypeScript, Rollup, Jest and ESLint (npm registry metadata, accessed 2026-10-11). The wizard is rendered in an iframe and authenticated with RS256 JWTs signed by the vendor's backend (SDK docs, JWT docs).
• Code solutions: TypeScript on Deno 2.x; the embed CLI binary (no Windows build; WSL on Windows) logs in through Auth0 (OAuth 2.0 Authorization Code Flow); SaaS clients are @anyflowinc/<name> packages added with deno add; sandbox limits 1 GiB memory, 60-minute run time, no filesystem writes (docs). The JSR scope @anyflowinc exists (created 2024-03-05) with no public packages listed (JSR; accessed 2026-10-11).
• Python: an opt-in Python action runs a restricted subset with import disabled (docs).
• Security tooling stated in the policy: admin console login limited to SSO with an IdP such as Google Workspace; 1Password for shared credentials; credentials encrypted with 256-bit encryption (security policy).

Inferred from current job postings (accessed 2026-10-11)

• Embed backend: Python, FastAPI, Django ORM, Celery; design described as DDD with hexagonal architecture (Software Engineer, SRE). The CTO's profile confirms a Celery-based workflow engine (Green).
• Embed frontend: TypeScript, React, Linaria, ESLint, Prettier, Jest (Software Engineer).
• Data: MySQL on Cloud SQL, Redis (Software Engineer).
• Infrastructure: GCP (GKE, GCS, Cloud SQL, Cloud IAP, Cloud NAT, Cloud Build, BigQuery, Cloud KMS, Cloud Pub/Sub), Kubernetes; CI/CD and IaC with GitHub Actions, Cloud Build, ArgoCD, Terraform; monitoring and security with Datadog, Stackdriver, Trivy (SRE).
• Automation team: TypeScript (Deno, Node.js) on GCP (Cloud Run, Cloud SQL, BigQuery, Cloud Logging, Cloud KMS, Cloud Scheduler, Cloud Storage, Cloud Armor, Identity Platform, Firestore), Resend; GitHub Actions, Cloud Build, Terraform (workflow-builder posting).
• Tools: Linear, Notion, Slack, GitHub; AI tools listed as available: Claude Code, GitHub Copilot, CodeRabbit, ChatGPT, Devin, Gemini (Software Engineer).

Hiring-only mentions: React (Next.js), Airflow and Digdag appear only as preferred qualifications (Software Engineer).

Systems

Documented operating limits: 10 MB soft limit per action step (1 MB with polling triggers), 100 MB hard limit on stored logs per step, 12-hour solution timeout (limits). Raw execution data is deleted 30 days after a run; daily encrypted backups are kept for up to 7 days (security policy). The availability target is 99.8%, measured quarterly, and the page states no SLA is defined (service level).

Technical background sought

• Software Engineer (Embed): required — designing, building and operating Web APIs; database schema design and operation; team development with Git; development using AI coding agents such as Claude Code. Preferred — complex web apps such as WYSIWYG editors; GCP/Kubernetes operations; asynchronous processing; CI-based automated testing; performance work and continuous refactoring; DDD; external API integrations; leading B2B development (posting).
• SRE: required — Kubernetes and cloud infrastructure operations, database schema design. Preferred — operating servers with more than 100 million monthly accesses, architecture spanning application and infrastructure, external API integrations (posting).
• Workflow-building engineer (Automation): required — client work such as contract development or SI (negotiating requirements and changes, balancing deadlines and quality), unit testing. Preferred — project management, API integration, data integration with CSV, databases, batch and job design (posting).
• Product Manager (Embed): required — Scrum or agile delivery, continuous improvement from customer feedback, practical understanding of API/SaaS integration (REST, OAuth, Webhook). Preferred — B2B SaaS PdM or technical customer support, DevOps or developer-productivity work (posting).
• CRE and technical customer success: required — technical support for web services or CRE/implementation-engineer work, and client work for the enterprise role; preferred — Python, external API integrations, managing development projects (CRE, TCS).

Industry domain

SaaS-to-SaaS and SaaS-to-core-system integration: third-party API authentication (OAuth, API keys), API version changes, pagination and rate limits, data mapping, CSV and database exchange for systems without APIs, and Japanese business SaaS such as accounting (freee, マネーフォワード, 弥生, 勘定奉行), HR (SmartHR) and POS (スマレジ) products. The Product Manager posting requires practical API/SaaS integration knowledge; for the engineering roles, external API integration experience is preferred, not required. Financial-sector experience is preferred for technical customer success, and regional-bank relationships for Enterprise BizDev (TCS, BizDev). Through the parent, part of the work concerns collecting activity data for Scope 1–3 CO2 accounting (Asuene, 2025-02-19). None of the reviewed postings says whether domain knowledge can be learned after joining.

Working conditions

Notes

Not publicly disclosed

Search scope for the findings below (2026-10-11): anyflow.jp and its sitemap, robots.txt, company, product, case, news and legal pages; docs-embed.anyflow.jp and its sitemap; the status page; the Notion careers page and all HERP postings; PR TIMES pages for Anyflow and Asuene; the 国税庁 法人番号公表サイト, ISMS registry and Google Patents; GitHub organisation lookups for anyflowinc, anyflow, anyflow-inc, anyflowjp and anyflow-jp, npm and JSR; note, Speaker Deck, Zenn, Qiita, connpass, Wantedly, Green, TokyoDev and Japan Dev; web searches for Anyflow, Anyflow株式会社, Anyflow Embed, 株式会社ピケ and Anybot in Japanese and English; INITIAL and HERP company profiles as leads.

• Revenue, ARR and customer count. No absolute figure found. The only growth figure is "前ARR600%以上の成長" in the 2024 Wantedly posting, with no base or period (Wantedly).
• Acquisition price and Smaregi investment. Neither amount nor stake is disclosed (Asuene, Smaregi alliance).
• Price list for Embed, Automation or Anyflow Connect.
• Engineering blog. None found. The note account has one post (2020-05-11); the Speaker Deck account has one image-only company deck dated 2024-02-13; no Zenn publication, Qiita organisation or connpass group was found.
• Open source. The GitHub organisation anyflowinc ("Anyflow Inc.", created 2017-05-01, X anyflowinc, email on anyflow.co.jp) has no public repositories (GitHub API). The GitHub user anyflow belongs to an unrelated individual. The npm package @anyflowinc/embed-sdk declares no repository or license.
• SLA. "現在 SLA を定めておりません" (service level).
• Third co-founder's name, the COO's background, visa sponsorship and English-language roles. Not found.

Inconsistencies across sources

• Founding date: 2016-02-12 (company page and releases); the corporate number was designated 2016-02-17 under the name Revode株式会社 (NTA); BRIDGE wrote that the company was founded in 2017 (2019-09-24).
• Rename date: the company notice says the name changed "2019年1月17日より" (notice); the register records the change on 2019-01-30 (NTA).
• Address: the register shows 新橋2丁目20番15号 since 2025-04-16; the company page, 2026 releases and the ISMS registry show 虎ノ門1-3-1 東京虎ノ門グローバルスクエア6階; current HERP postings and the careers page show 虎ノ門1-10-5 KDX虎ノ門一丁目ビル WeWork 3階 アスエネ株式会社内; 2025 releases show the same building's WeWork 4階 (2025-06-11).
• Cumulative funding: 約2.6億円 after the pre-Series A (company and Forbes JAPAN, both 2020-01-08) versus 2億7,000万円 (BRIDGE, 2020-01-08); 約3.4億円 before the acquisition (Asuene, 2024-12-10); HERP's company profile shows 2.8億円, estimated from registry filings (HERP profile; accessed 2026-10-11).
• Headcount: "30名強" including contractors (careers FAQ); "30名(業務委託含む)" (Software Engineer, posted 2025-12-22); Dev ~20 + Biz ~10 (TCS, posted 2026-07-22); Dev 13 + Biz 12, ~25 (Product Manager, posted 2025-12-12); Dev 11 + Biz 10, ~20 (CRE, posted 2025-12-12). HERP's profile shows 18 employees based on pension-insurance enrolment for 2024-08 to 2026-08 (HERP profile). In May 2024, Wantedly listed 15 members and 20 including contractors (Wantedly).
• Connector count: "100以上" (Automation page), "140種類以上" (2025-02-19), "200種以上" (2026-05-28), and 165 connector pages in the site sitemap (accessed 2026-10-11). The sources do not define what is counted.
• What Anyflow Automation is: "SaaS事業者向けのHeadless iPaaS" for enterprise core-system integration (Automation page) and customer data-integration projects (workflow builder), versus "自社の業務を自動化、効率化するためのプラットフォーム" (careers page) and "社内業務の自動化を支援する" (Software Engineer).
• Survey figure: the 2026-07-14 release's headline and lead say 91.9% excluded a SaaS for insufficient API integration; its summary and detailed results give 75.7% for that question (2026-07-14).
• ISMS standard: the docs security policy cites JIS Q 27001:2014 (ISO/IEC 27001:2013) (policy); the registry shows JIS Q 27001:2025 (ISO/IEC 27001:2022+Amd 1:2024) (registry).
• My Event release date: announced as a new feature on 2024-01-16 (PR TIMES); a later release says it shipped in December 2023 (2024-08-20).

Other

• Product sequence: cloud RPA Anybot (pre-registration 2018-10, as 株式会社ピケ) → the original Anyflow iPaaS for businesses (β 2019-10) → Anyflow Embed for SaaS vendors (GA 2023-07-13) → Anyflow Automation, AI/RAG data sync (2026-05) and code solutions (β 2026-07). The CTO states Embed was built from scratch and launched about four months after planning began (Green).
• Patent wording changed from "特許出願中" (2022-12-08, 2024-01-16) to "特許取得済" on the Embed page, consistent with the JP7645548B2 grant listed by Google Patents.
• Asuene's group-company list in its 2026-06-26 release calls Anyflow an "AIデータ連携プラットフォーム" (Asuene).
• The status page's incident feed lists 20 incidents from 2024-01-18 to 2026-08-25, seven of them about scheduled triggers not firing (status page; accessed 2026-10-11).
• The full Embed documentation is public on GitBook, including an llms-full.txt export; product pages link to it ("ドキュメントへ").
• PR TIMES lists 38 Anyflow releases as of 2026-10-11; there were none between 2025-06-11 and 2026-05-28 (PR TIMES).
• Not accessible on 2026-10-11: a CodeZine article (bot check), the TokyoDev profile URL (HTTP 403), the TechCrunch Japan 2019 article (certificate error) and the Forbes Asia profile text.

Resources

Official

• Homepage · company page · sitemap
• Anyflow Embed · Anyflow Automation · connectors · case studies
• Terms of use · privacy policy
• Embed documentation · docs sitemap · release notes · code solutions · SDK · SDK changelog · JWT · Vender Server API · deployment environments · wizard hosting · Python action · limits
• Security policy · service level · incident response · status page
• Careers page (Notion) · HERP job list — Software Engineer, SRE, Product Manager, workflow builder, PM lead, CRE, TCS, Enterprise BizDev
• GitHub organisation · GitHub API · npm · JSR scope · note (JA) · Speaker Deck · company deck, 2024-02-13

Press releases (anyflow.jp, JA — newest first)

• Code solutions β — 2026-07-28
• SaaS buyer survey — 2026-07-14
• Webinar with Cloud Circus — 2026-06-29
• AI agent / RAG data sync — 2026-05-28
• End of Smaregi integration apps — 2026-03-31
• Share No.1 — 2025-06-11
• SmartHR case study — 2025-05-23
• Code action — 2025-04-17
• Acquisition by Asuene — 2024-12-10
• Embed first anniversary — 2024-07-16
• Money Forward Cloud — 2024-03-12
• NP掛け払い — 2023-11-29
• SmartHR Plus app — 2023-08-29
• Embed GA — 2023-07-13
• Forbes 30 Under 30 Asia — 2022-05-26
• FUJITSU ACCELERATOR award — 2020-02-10
• Pre-Series A — 2020-01-08
• Seed round — 2019-09-24
• Rename to Anyflow — 2019-01-17

PR TIMES (JA)

• Company release list
• ASUENE adopts Embed — 2025-02-19 · Error notifications to six tools — 2024-12-26 · Request & Response — 2024-08-20 · My Event — 2024-01-16
• Yayoi alliance — 2023-07-19 · Smaregi capital alliance — 2022-12-08 · IT導入補助金 — 2020-08-06
• EY Innovative Startup 2020 — 2020-02-28 · Pre-Series A — 2020-01-08 · B Dash Camp — 2019-11-05 · Seed — 2019-09-24 · Anybot, as 株式会社ピケ — 2018-10-24
• Asuene: 100% acquisition — 2024-12-10 · integrations via Anyflow — 2025-02-19 · head office move — 2026-05-07 · group company list — 2026-06-26

Registers

• 国税庁 法人番号公表サイト — 1011001109588 (JA)
• ISMS registry — IS 751085 (JA)
• Google Patents — JP7645548B2 · JP2024004078A

Third-party coverage and profiles

• BRIDGE — seed round, 2019-09-24 (JA) · pre-Series A, 2020-01-08 (JA) · Embed GA, 2023-07-13 (JA) · acquisition, 2024-12-12 (JA)
• Forbes JAPAN — pre-Series A, 2020-01-08 (JA)
• Founder — CEO interview, 2019-06-17 (JA)
• Green — member profiles incl. CTO (JA) · Embed business lead interview (JA)
• Wantedly — Tech Lead posting, 2024-05-11, closed (JA)
• HERP — company profile (JA) · INITIAL (JA)