AGCRNsoftware by angelcrown

AGCRN / BUILT AND OPERATED BY ANGELCROWN

Independent browser software by angelcrown.

I use AGCRN to publish the software I maintain, explain what each product actually does, and document where user data is processed. Products use separate subdomains; ownership, policies, and support stay here.

3live products
33HaloBench utilities
3documented data models
1independent operator

LIVE PRODUCTS

Working software, not concept pages.

Each product has a public URL, a concrete workflow, a product record, and a stated data boundary.

01 / BROWSER UTILITIES

HaloBench

A searchable collection of focused tools for text, dates, calculations, images, color, and developer work.

  • 33 working utilities
  • Korean and English primary interfaces
  • Browser-stored search and favorites
02 / LOCAL IMAGE WORKFLOW

PicFit

Turn one source image into the sizes required by creator platforms and app stores, then download the selected outputs together.

  • Preset and custom dimensions
  • Crop focus, quality, and format controls
  • Image processing in the browser
03 / ENCRYPTED WORKSPACE

myOS

Connect schedules, projects, study, finance, notes, ideas, and frequently used accounts in one personal workspace.

  • Life-aware schedules and projects
  • Encrypted workspace synchronization
  • Optional user-configured AI providers

OPERATING STANDARD

One publisher.
Clear product boundaries.

AGCRN is the accountability layer shared by products with different identities, workflows, and data models.

  • Show the working productA project is listed after its core workflow can be used at a public URL.
  • Describe the real data pathLocal processing and encrypted synchronization are documented as different models.
  • Separate advertising from the taskAn ad must not imitate a control, change an output, or require a click to continue.
  • Keep one contact pointOwnership, policy questions, corrections, and security reports lead back to angelcrown.

BUILD NOTES / UPDATED 2026-08-30

Decisions behind the products.

Read why the domain is structured this way, how the three product data models differ, where advertising is allowed, and what “live and maintained” means for an independent product.

  1. 01
    One root domain, separate product subdomainsPublishing structure
  2. 02
    Local processing and encrypted synchronizationPrivacy architecture
  3. 03
    Why empty and account-only screens are not ad surfacesAdvertising boundary
  4. 04
    How product records and known limits are maintainedOperations
Read all build notes