📦 Automation packs are now KRW 4,500 each on ctee.kr. Updates stay free.
Dex › Products

Beginner package questionnaire (Korean)

Price update: KRW 4,500 from October 5, 2026, 09:00 KST (00:00 UTC). Until then: KRW 4,500. Read the announcement →

← All products

BUILDERLOG · CHANNEL AUTOMATION PACK

Blog Automation Pack

Code and operating guides for a Naver keyword queue, drafting, images, review, scheduling and RSS verification.

KRW 4,500 · Single-user license · External service costs are separate

Before you buy

This is code and documentation to configure on your computer. Account setup and terminal work are required. Setup services, AI subscriptions and API credits are not included. Setup time, views and income are not guaranteed.

One cloud CLI, Python 3.11+, Node 20+ and macOS/zsh. Publishing requires a Naver account and an authenticated Aside CLI profile. Ollama and image APIs depend on your production route.

Read requirements, costs and the user guide →

Delivery Instant download after payment (Mac and Windows ZIP) · Refund policy (KO)
🆓 Prefer to build it yourself? The free dex prompt Build a Blog Auto-Publishing Pipeline walks an AI through building it from scratch. The pack is the ready-to-run version with updates.

Get it on ctee · KRW 4,500 · Mac & Windows ↗

🔄 Already bought it? Get the latest version
  • Bought on ctee — sign in to ctee, open the ≡ menu → 구매·문의 내역 → 콘텐츠 상품 and download again. We swap in the new files on every update.
  • Bought on Gumroad before — enter your purchase email at My purchases and we email you a link to the latest version.

Do I need both Claude and Codex?

No. Start with one cloud CLI you can access. Claude Code needs eligible subscription access or Console API billing. Codex CLI supports an eligible ChatGPT plan or API billing. Subscription and API charges are different. The current Instagram pack also needs Ollama for local drafting.

Compare required/optional tools and official documentation →

Included

Your first run

  1. Check your environment, accounts and additional charges
  2. Extract into a new folder and configure your settings
  3. Check with publishing, uploads, comment DMs and schedulers off
  4. Generate and review one output
  5. Verify integrations and permissions before enabling real publishing or scheduling

Precautions and support

Sign in and verify accounts yourself. Review facts, sources, asset rights and disclosures. Do not share keys, cookies or full .env files. Platform UI/API changes can require adapter updates. For support, provide the pack/version, OS, failed stage and error logs with secrets removed.

Step-by-step guide and troubleshooting → · Contact

Preview the five-step onboarding course (Korean) →