Published first technical blog post
Launched the engineering blog with "Choosing AWS Amplify for a Developer Platform Marketing Site" — the first in a series of posts exploring the architectural decisions behind building smplkit.
What's new
Recent development milestones and platform updates.
Revised API key authentication model
Distinguished API keys (account-scoped, management access) from SDK keys (environment-scoped, runtime access). Each key type has its own prefix, scoping rules, and console placement.
Implemented sleep/wake workflows for dev environments
Added GitHub Actions workflows that automatically discover and scale down ECS services, stop RDS instances, and halt bastion hosts to reduce infrastructure costs during off-hours.
Published API design standards
Adopted JSON:API as the response format for all public APIs. Established the error robustness invariant: client input must never produce a 500, and every error response returns a JSON:API body.
Deployed interactive API reference
Launched the Scalar-powered API reference at docs.smplkit.com with live OpenAPI spec rendering, dark theme, and built-in request execution.
Established internal and external API isolation
Separated internal service-to-service APIs from public-facing endpoints using dual load balancers per service. Internal APIs are unreachable from outside the VPC by network design.
Completed OIDC authentication migration
Replaced AWS Cognito with direct OIDC integration for Google and Microsoft identity providers, reducing external dependencies and improving multi-cloud portability.
Launched developer console
Shipped the initial developer console at app.smplkit.com with account management, environment configuration, and API key provisioning.
Deployed App Service database schema
Completed the nine-table App Service schema: account, user, account_user, environment, api_key, subscription, subscription_usage, service, and invitation.
Established database schema conventions
Standardized conventions across all services: singular table names, UUID primary keys, text over varchar, standard column sets, and JSONB data columns for extensibility.
Project initialized
First code committed. Repository structure, CI/CD pipeline, and AWS infrastructure provisioned via Pulumi.